=== Fujitsu [n=Fujitsu@c58-107-168-5.eburwd7.vic.optusnet.com.au] has joined #launchpad === Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad === spiv [n=andrew@218-214-66-203.people.net.au] has joined #launchpad [02:25] Morning everyone. === mpt_ [n=mpt@203.118.156.188] has joined #launchpad === jsgotangco [n=jsg123@ubuntu/member/jsgotangco] has joined #launchpad === mpt__ [n=mpt@203.118.156.188] has joined #launchpad === bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #launchpad === purple_cow [n=david@zero.navi.cx] has joined #launchpad [04:14] Can I get some administrative help? I need the no language deleted from https://launchpad.net/products/xchat-gnome/trunk/+pots/xchat-gnome === rpedro [n=rpedro@87-196-12-221.net.novis.pt] has joined #launchpad === bluefoxicy [n=bluefox@c-68-33-112-13.hsd1.md.comcast.net] has joined #launchpad === sevrin [n=sevrin@202.75.186.154] has joined #launchpad === Fujitsu [n=Fujitsu@c58-107-168-5.eburwd7.vic.optusnet.com.au] has joined #launchpad [05:59] Goooooooooooooooooooood afternoon Launchpadders! [06:15] hi [06:24] I want to make a spec on pqm [06:25] but have it visible in the bzr project [06:25] is that possible ?? [06:25] erm [06:25] bzr product [06:36] mpt: any suggestions for https://launchpad.net/products/bzr/+spec/0.10-release-process ? === ChanServ [ChanServ@services.] has joined #launchpad === xenru [n=Miranda@85.192.12.76] has joined #launchpad [07:20] lifeless, arrange the dependency levels horizontally instead of vertically [07:21] That way you know they're only ever going to be three ovals wide, so they're less likely to overflow [07:22] Also, the specification shouldn't link to itself [07:22] and "Remove Dependency" should have a "-" icon, not a "+" icon [07:23] mpt: https://launchpad.net/distros/ubuntu/+spec/automated-problem-reports === bluefoxicy sees 4 ovals deep [07:24] Oh, so it's unlimited depth? [07:24] Then there's no hope [07:25] But, rounded rectangles would be more compact than ovals [07:25] to be fair I think I'm the only one to cause that situation with my whoring of pitti's spec :) [07:25] mpt: there's another spec that I haven't made that would have I think 6 horizontal dependencies [07:26] I haven't added it to +spec/ because, well, people would think I'm crazy. [07:26] And, the clickable items in the graph should look more clickable. [07:26] And, "Dependency tree:" shouldn't end in a colon. [07:26] invert colors when mouse passes over? :P [07:27] oho it's a map === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [07:32] No, that wouldn't make them look more clickable until it was too late === mpt [n=mpt@203.118.156.188] has joined #launchpad === danilos [n=danilo@82.117.204.171] has joined #launchpad [08:09] lifeless / BjornT / spiv, where is the latest location of the zope tree? [08:09] bzr pull --remember sftp://sodium.ubuntu.com/home/warthogs/archives/rocketfuel/zope/3.2/ gives me "0 revision(s) pulled" [08:10] mpt: what does bzr revno in your zope tree say? [08:10] BjornT, 36 [08:12] mpt: ok, then it should be up to date, i think. that's the revision containing stub's test setup changes. === mpt_ [n=mpt@203.118.156.188] has joined #launchpad [08:13] mpt_: ok, then it should be up to date, i think. that's the revision containing stub's test setup changes. === Nafallo [n=nafallo@ubuntu/member/nafallo] has joined #launchpad [08:17] ok, thanks BjornT [08:24] BjornT: do you know how i use stub's mechanism to leave a message to be displayed on the next page load? [08:25] ah [08:25] BrowserNotificationMessages === glatzor [n=sebi@ppp-62-245-210-231.dynamic.mnet-online.de] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [09:01] morning === rpedro [n=rpedro@87-196-40-98.net.novis.pt] has joined #launchpad === fabbione [i=fabbione@gordian.fabbione.net] has joined #launchpad === Sp4rKy [i=Sp4rKy@ubuntu/member/sp4rky] has joined #launchpad [09:17] elmo ping ? [09:24] lifeless: not currently possible, would you like to write a spec on how that would look-and-feel? [09:27] hey sabdfl [09:29] hi sivang === carlos [n=carlos@84.Red-83-40-82.dynamicIP.rima-tde.net] has joined #launchpad [09:29] morning! [09:30] morning carlos [09:30] sivang: hey dude!, how's going? [09:30] carlos: fine, fine, you? [09:31] well... I would prefer to have more vacations ;-) [09:31] sabdfl: added that as a TODO [09:32] carlos: heh [09:32] but is time to start working again... === fabbione [i=fabbione@gordian.fabbione.net] has joined #launchpad === quail [n=quail@unaffiliated/quaillinux/x-000001] has joined #launchpad === Spads [n=crack@217.205.109.249] has joined #launchpad === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [10:13] Good morning. [10:13] morning ddaa [10:17] Hi sivang === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has left #launchpad [] === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad [10:18] please [10:18] i've an @ubuntu.com adress but doesn't appears to LP [10:19] Seveas: do you run ubugtu ? [10:19] lifeless, yes [10:19] suggestion for you [10:19] in a single channel, if a bug is mentioned twice in a short period, STFU about it :) [10:20] (optionally check if its changed its summary or status I guess) [10:20] that's a plan [10:20] ubugtu can get quite disruptive otherwise [10:21] I'm not near the code now, could you file it as a bug (product: ubuntu-bots) [10:21] done === malcc [n=malcolm@host86-134-233-12.range86-134.btcentralplus.com] has joined #launchpad [10:23] ta [10:24] Sp4rKy: did you added and confirmed it ? [10:25] lifeless: hi [10:25] carlos: hi [10:25] lifeless: should the 'launchpad' user have access to staging's database as the user 'postgres' ? [10:25] no [10:26] hmmm... I think stuart suggested that in one email... perhaps he was talking about my user. Let me try.. === plaes [n=plaes@212.7.7.16] has left #launchpad [] [10:26] access as postgres will give you access to all the user passwords etc [10:26] so its tightly constrained even on staging [10:26] lifeless: ok, it has, but if you select the right database [10:26] carlos i have to add it manualmly ? [10:27] Sp4rKy: I think so === carlos out for 15 minutes [10:30] but it is forwarded to my other adress :/ [10:31] Sp4rKy: yeah, @ubuntu.com addresses aren't automatically added to launchpad at the moment. So long as you can receive mail there, you should be able to add it to your existing launchpad account just fine, though. [10:32] k === stub [n=stub@82.109.136.116] has joined #launchpad === mpt [n=mpt@203.118.156.188] has joined #launchpad === niemeyer [n=niemeyer@82.109.136.116] has joined #launchpad === matsubara [n=matsubar@82.109.136.116] has joined #launchpad === jamesh [n=james@82.109.136.116] has joined #launchpad === Kinnison [n=dsilvers@spoo.flarn.net] has joined #launchpad === doko [n=doko@dslb-088-073-097-194.pools.arcor-ip.net] has joined #launchpad [11:07] malcc: morning. did kiko catch you on friday? === Sp4rKy [i=Sp4rKy@ubuntu/member/sp4rky] has left #launchpad [] === carlos_ [n=carlos@230.Red-83-39-63.dynamicIP.rima-tde.net] has joined #launchpad [11:09] lifeless: jamesh: mpool: spiv: bazaar meeting in 51 minutes, please put proposed agenda items on the wiki [11:09] jamesh: is SteveA somewhere around? [11:11] lifeless: about our previous talk [11:12] sabdfl: Morning, I saw his email about a soyuz design session this week [11:12] lifeless: launchpad user on asuka has rights to connect as postgres user [11:12] I got an error because I was connecting to the wrong database [11:12] malcc: tomorrow ok? [11:13] sabdfl: Tomorrow is fine, but I'll have to be back in town for 6pm [11:14] i was thinking we would do it at Docklands, sound OK? [11:14] Yes, that's fine. Is that the novotel near the exhibition center where I was interviewed? [11:18] ddaa: he is here, but talking [11:20] yes [11:27] danilos: I just handled XaraLX translations, if he confirms that everything is ok, I will request the removal on production [11:28] carlos: ok, can you also send me the queries, so I at least have them in case of a need [11:28] sure [11:28] carlos: also, I'd like to have your latest stuff for edgy opening if it's not in your branch (it isn't, right? ;) [11:28] it should be there... [11:28] carlos: ah, ok, sorry for assuming incorrectly then :) [11:28] the only changes I have on staging is to disable the statistics updates [11:29] do I need to talk to mpt about a change that adds something visually to a page? (that is, it's outside controls and such) [11:29] I need to push my changes to test them on staging ;-) [11:29] malone #3186 [11:29] Malone bug 3186 in blueprint "New spec form has undescribed no-capitals constraint" [Medium,Confirmed] http://launchpad.net/bugs/3186 [11:29] carlos: sure, go ahead :) [11:30] carlos: I've got another "critical" bug to work on, so I'll do that now [11:30] cool [11:30] ah oops, not a change actually, only a small addition. cool === mpt [n=mpt@203.118.156.188] has joined #launchpad === SteveA [n=steve@82.109.136.116] has joined #launchpad [11:50] lifeless: have you had a chance to look at packaging the tickcount module yet? [11:50] labas SteveA [11:51] jamesh: meep meep meep. [11:51] I got distracted by debian changing python policy [11:51] h isivan [11:51] jamesh: I'm packaging it for Ubuntu right ? [11:51] lifeless: what's the python policy change? === Kamion [n=cjwatson@83-216-156-196.colinw664.adsl.metronet.co.uk] has left #launchpad [] [11:52] SteveA: rather than having python-FOO and python2.4-FOO for regular python packages, there is now a system that builds a symlink farm for all installed pythons [11:52] I see [11:52] and thus you have just one python-FOO package which supplies the module to all pythons [11:52] does this work in all cases/ [11:52] ? [11:53] lifeless: What are you packaging ? [11:53] sivang: tickcount [11:53] I'd guess there are exceptions where there are different released versions for different pythons [11:53] lifeless: ah, cool [11:53] sivang: a diagnostic extension SteveA wrote [11:53] lifeless: I know, I already looked at it :-) [11:53] SteveA: right. its made the common case much simpler. The uncommon case still needs separate packages for each python [11:53] https://help.launchpad.net/ComingFeatures/EssentialSpecificationSubscribers [11:53] need a star that is less obviously from google :-) [11:54] SteveA: i.e. binary modules, or incompatible python codebases for different pythons etc [11:54] sabdfl: oh, goody [11:55] lifeless: I think that was the plan [11:55] jamesh: 'we' have been involved with it [11:55] I dont know if edgy is doing the transition yet... I'll ask [11:56] jamesh: will you update your scheduler to look at SpecificationSubscription.essential when that lands, please? [11:56] ok, edgy has. cool [11:57] sabdfl: sure. [11:57] jamesh: there is also a DISCUSSION state for specs [11:57] so drafting vs discussion can be explicit [11:57] i.e. if the state is discussion, then it needs a discussion session [11:57] if the state is drafting, then it needs drafting [12:01] carlos: ping [12:01] danilos: pong [12:02] sabdfl: this is result of the weekend hacking? :-) [12:02] carlos: on xaraxl issue: do you have a list of translators whose translations we should keep? [12:02] ddaa: is it meeting time ? [12:02] carlos: perhaps it's better to do queries in the form of "person NOT IN ..." [12:02] Yup [12:02] Finishing preparing. === Spads [n=crack@82.211.81.248] has joined #launchpad [12:03] danilos: I prefer to remove only the ones that I was told to remove [12:03] danilos: and remove later anything else [12:03] than remove something by mistake [12:03] carlos: well, from the last email he sent I got the impression that he sent the list of translators who are allowed to translate it [12:03] just because someone forgot to gave me that name... [12:03] jamesh: -> #launchpad-meeting [12:03] danilos: he sent the list of allowed, and the list we should remove [12:04] but we cannot undo removals [12:04] carlos: yeah, it makes sense, but it's a much more clear-cut [12:04] so I prefer to take the less destructive operation ;-) [12:04] I agree, but how come there is a romainian single translated entry? [12:05] s/romainian/romanian/ [12:11] danilos: URL? [12:11] carlos: well, read the Neil's response [12:12] I see... [12:12] let me check [12:14] carlos: https://staging.launchpad.net/products/xaralx/0.4/+pots/xaralx/ro/+translate?batch=10&show=translated, space is translated [12:14] yeah, I saw it [12:14] carlos: though, it's on production as well [12:15] how does one tell who did the translation? [12:15] yeah, seems like that guy did translations after we close it [12:15] danilos: well, that's one of our remaining UI bugs === mpt [n=mpt@203.118.156.188] has joined #launchpad [12:16] carlos: ah, ok, I don't think I am assigned to that one :) [12:16] Can anyone please tell me, where I find the files/templates responsible for example, for what the +addspec page contains when access? (specifically stationary text on that page) [12:18] sivang: look inside zcml/ directory [12:18] sivang: you should look on the zcml for the addspec [12:18] there you have the link between the pagetemplates and the URLs [12:19] carlos, matsubara : gazil thanks. === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [12:25] stub: https://sodium.ubuntu.com/~andrew/paste/filexJOZb6.html [12:25] please review, and if ok let me have a number? thanks [12:26] sivang: it's the visible tip of the weekend, yes === sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has left #launchpad [] [12:34] stub, carlos: if I run a query, and later modify it slightly, how do I purge postgres' cache so I can time it again? [12:35] danilos: no idea [12:35] danilos: perhaps restarting postgres... [12:35] carlos: well, I guess I can't do that with staging ;) [12:36] right ;-) [12:36] grumph [12:36] danilos: anyway, timing things on staging in the morning is not a good idea [12:37] danilos: language packs are being generated atm [12:37] Who knows about KarmaContext? salgado I guess [12:37] matsubara, carlos : I've found specification-add.pt but I can't see where to change the text explaining about the rules for the .name attribute [12:38] hey mpt [12:38] carlos: well, I am looking for really big differences (like a hundred times faster, so I don't care about the 10x slowdown) don't know if language-pack generation cares :) [12:38] hi sivang, how's hacking [12:38] mpt: carlos should know about karmacontext as well :) [12:38] mpt: good , good, started to get along with testbrowser, even converting 2 tests in specs/ to testbrowser, just to make my patch look cooler to kiko ;-) [12:39] mpt: part of a fix to malone #52038 [12:39] Malone bug 52038 in blueprint "Please rename "Braindump" state to "New"" [Wishlist,In progress] http://launchpad.net/bugs/52038 [12:39] danilos: no, language packs doesn't care about it [12:40] sivang: is an edit or add form ? [12:40] carlos: add form [12:40] carlos: "Register a feature specification.." [12:40] sivang: in that case, I guess the form is autogenerated and you can get those descriptions from the interface [12:40] inside the interfaces/ directory [12:41] right, looking there then [12:41] we use the interfaces documentation to render those forms [12:41] cool, tanks [12:41] err, thanks that is [12:41] mpt, danilos: I know a bit of that, but just because I talked with salgado about the spec [12:41] mpt: what do you need? [12:42] carlos, two of my branches failed PQM in lib/canonical/launchpad/doc/karmacontext.txt [12:42] And I wasn't touching karma stuff in either of them [12:42] could I see the error? [12:43] one moment [12:43] carlos: sorry, I thought you were also the one to implement it [12:43] I don't know anything about those tests but perhaps I see something obvious that gives you a clue... [12:43] danilos: no ;-) [12:43] mpt: I have a fix for the karmacontext bug, but couldn't land it due to 30-mergepeople.txt errors [12:44] heh [12:44] the test in question is unreliable [12:44] jamesh, is that 30-mergepeople.txt problem the one that's been around for months? [12:44] guys, guys, can't you write bug-freeTM code? :P [12:44] jamesh: hah. [12:44] mpt: I think so [12:45] ok, I'll queue up after you then jamesh [12:45] unless it's an easy fix that I can try landing as well [12:45] danilos: it's writing bug-free tests that's the tricky bit sometimes ;) [12:46] Writing test-free bugs, on the other hand, that's easy [12:46] bug 51130 [12:46] Malone bug 51130 in launchpad-bazaar "cannot rename a branch I own" [Critical,Confirmed] http://launchpad.net/bugs/51130 [12:46] spiv: then lets skip that step \o/ [12:46] mpt: yeah :) [12:46] mpt: this is the fix I made: https://sodium.ubuntu.com/~andrew/paste/filerkk5v9.html [12:49] jamesh: ok, so dyson [12:49] jamesh: I think: 1/ eliminate recursion, 2/ leave the version constraints etc at the moment - see how it goes [12:50] jamesh: we can add recursion if needed, or do globl matching for x dirs - i.e. location/*/*.tar.gz in the future [12:50] lifeless: it sounds like eventually we want another field to say whether recursion is required [12:50] right, but lets iterate [12:50] how does that sound ? [12:51] is it compatible with the feedback you got ? [12:51] sounds good. [12:52] turning off recursion should hopefully get it to do something [12:52] ok, thats good. I realise it will be a bit before you get back to it, but I'm really keen to get this deployed - so please let me know if you get other things assigned to you that will delay this [12:52] reviewer meeting in 8 minutes [12:53] thanks jamesh [12:54] mpt: you could try putting that fix in and see if you can merge successfully [12:54] mpt: perhaps that'll make the 30-mergepeople.txt test go away for me :) [12:55] Yes, I've stuck it in both branches (momentarily flummoxed by that test not yet existing in one of the branches:-) [12:55] ah, foo, with a repository I can't push multiple branches simultaneously === sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad [12:56] carlos, matsubara : yay, found it. [12:56] reviewer meeting in 4 minutes [12:57] sivang: hint, use "grep -r 'the string you want to find'" [12:57] it's really helpful to learn where are those strings [12:57] I often type "grep -Irn ...", it's a handy combination of flags. [12:58] The -I is a really lazy way to filter out .pyc files :) [12:58] carlos: tried with -ril, which gave nothing when I searched for "mozilla-type-ahead-find, postgres-smart-serial." that appear is examples for spec names. [12:58] ahhhh, nifty [12:58] I see [12:58] carlos: was probably a bad search string... === sivang mans about -I [12:59] spiv: oh cool! [12:59] review meeting time [01:00] lifeless: any plans to do the conversion of old branch data onto sodium? [01:00] SteveA: after the meeting please [01:00] * Roll call [01:00] * Agenda [01:00] * Next meeting [01:00] * Queue status. [01:00] i typed that before you said "meeting time" :-) [01:00] 20:59 < lifeless> review meeting time [01:00] 21:00 < SteveA> lifeless: any plans to do the conversion of old branch data onto sodium? [01:00] not as far as my irc client knows :) [01:01] I'd like to add to this agenda "reviewing Trivial branches" [01:01] or "trivial commits" [01:01] ok [01:01] whose here ? [01:01] spiv: ping [01:01] jamesh: ping [01:01] me [01:01] BjornT: ping [01:01] my here [01:01] here [01:01] next meeting - monday coming, same time ? [01:02] +1 [01:02] here [01:02] 2006-08-15 at 1100 UTC. it is [01:02] sure [01:02] ok [01:02] queue status [01:03] 11 branchs in the main queue [01:03] oldest is 51 days which I believe to be bogus [01:03] jamesh: any input on that rather large # ? [01:04] lifeless: I think the branch was entered with a cut-n-pasted date originally and my code believes the dates for new branches [01:04] this has happened before [01:04] either that or it picked up the date from the last time cprov put the branch up [01:04] I'm curious about why after 9 days salgado still hasn't reviewed a one-line change of mine ;) [01:04] it really screws up the process. Can you make analysing and fixing this a high priority please? (If SteveA agrees) [01:05] since he's used "cprov/launchpad/queue-ui" as a long running branch [01:05] jamesh: can you perhaps [01:05] other than that : Oldest (non-bogus date) is 16 days with steve, then 12 with kiko and 10 with jamesh. Our sevice level is slipping [01:05] extract the date of the earliest unmerged revision in the relevant branch? [01:05] I mailed the reviews list last week with a nag. [01:06] spiv: jamesh: I've no opinion about the best way to implement - can you discuss post-meeting ? [01:06] the 16 day thing is blocked on some production changes [01:06] SteveA: doing the review is blocked ? [01:06] yes. I don't want to look at it before I know what it needs to fit with. [01:07] ok. This should be work-in-progress then surely ? [01:07] I'm -0 on jamesh analysing and fixing a problem caused by people not using [@DATE@] correctly [01:07] I think we should tell people just to use [@DATE@] by email and in the next launchpad dev meeting [01:07] (if what its fitting with is not done yet, how can it be ready to review ?) [01:07] and only if that fails to address the problem [01:07] to look for a technological solution [01:08] lifeless: that branch can be moved to w-i-p [01:08] it can be WIPed from my queue [01:08] SteveA: in this sort of situation, please do that rather than sitting on the branch. [01:08] ok [01:08] I'm moving it now [01:09] ok [01:09] is there a similar issue with flacoste/launchpad/tt-search ? [01:09] which is in kiko's queue [01:10] no idea [01:10] jamesh: david/launchpad/importd-bzr-native is in your queue. You've been overseas for an extended duration right ? [01:10] (Thinking of [@DATE@] , it appears salgado forgot it entirely for a branch of his in my queue, so I'm +1 on a reminder about it by email/at the lp meeting) [01:11] ok, lets do an email reminder - SteveA can you do the agenda thing for lp, I'll send an email to launchpad@ after this meeting [01:11] lifeless: yeah. I'll try and get to my two oldest ones early this week, but the other two would probably be better to reallocate [01:11] ok [01:11] jamesh: ok. BjornT is back, BjornT - are you willing to take flacoste/launchpad/tt-bug-fixes and cprov/launchpad/small-fixes ? [01:12] lifeless: sure [01:12] thanks - can you update PendingReviews ? [01:12] ok, that should reduce it from crisis situation [01:12] ok [01:12] updated [01:12] I'll send another nag email tomorrow, directly rather than just noted in the message header for everyone [01:13] thats to grab kiko and salgados attention [01:13] SteveA: you will be around when kiko and salgado show up right? can you draw their attention to reviews for me please ? [01:13] I'll be in meetings here [01:13] so probably not [01:13] oh. [01:13] ok [01:13] BjornT: could you ? [01:14] lp infrastructure sprint in progress [01:14] I'm just taking time out for the bzr and review meetings [01:14] lifeless: sure, i'll do that [01:14] thanks! [01:14] ok. [01:14] trivial branch reviews (stevea) [01:14] ok [01:15] we've talked in the past about adding links to the emails from PQM [01:15] so that reviewers can, with a single click, see the code changes that have been committed [01:15] this will plug a gap in our reviews, in checking that [trivial] commits really are trivial [01:15] often someone thinks something is trivial, but it really is not [01:16] even though it is just a few lines of code, it has other issues [01:16] today, lifeless set up a branch browser on devpad.c.c [01:16] I've asked the admins to make the browser available to the outside world via apache + certificate [01:16] I'd like someone to make PQM emails contain links to appropriate places in the branch browser [01:17] lifeless: what needs changing in our PQM setup to make this so? [01:17] the email sending plugin needs code changes to add the link [01:18] the exact structure I dont have mapped in my head, but it will require changes [01:18] where is the code that needs hacking on? [01:18] i'd like to give this to jamesh to hack on [01:18] https://launchpad.net/products/bzr-email [01:18] is the current email sending facility [01:19] we mirror the structure from balleny to sodium [01:19] so some local path algebra should be enough to setup the correct browser url, without needing PQM's magic URL knowledge. [01:20] jamesh: while you are at it, if you could review matthieu moys improvements which are in malone, that would be great - and it may well help what you are doing [01:20] there is a spec on what we want from PQM emails [01:20] lifeless: okay. For the browser URL, I think we just need a URL base and the PQM commit revision ID [01:21] yes, that requires signficantly more effort and a complete change in how the emails are generated and sent [01:21] jamesh: thats what I'm thinking too - just a new parameter to the plugin to add this link, turned on by the present of the URL base [01:22] ok, anything more on this ? [01:22] any idea where that spec is? === SteveA looks [01:23] https://launchpad.canonical.com/PQMCommitMessages [01:23] lifeless: I guess letting the user provide a format string would be a good way to do it genericly (substituting in public branch URL, revision number and revision ID as needed) [01:23] jamesh: start with the simplest approach IMO [01:23] jamesh: which I'll happily let you define [01:23] that's all from me [01:24] ok, any other business ? [01:24] 5 [01:24] 3 [01:24] 2 [01:24] 1 [01:25] thanks for coming, meeting is done === spiv -> dinner === imbrandon [n=brandon@ubuntu/member/pdpc.active.imbrandon] has joined #launchpad === imbrandon [n=brandon@ubuntu/member/pdpc.active.imbrandon] has left #launchpad ["Konversation] === carlos -> lunch [01:28] later! [01:31] mpt: still around? [01:32] lifeless: and after the review meeting... [01:32] lifeless: any plans to do the conversion of old branch data onto sodium? [01:33] yes, plans, but currently I have no time allocated to that [01:33] nor any expected for another 7 weeks === cprov [n=cprov@monga.dorianet.com.br] has joined #launchpad [01:34] lifeless: does it have to be you who does this, or could someone else? [01:34] someone else can ensure that all the data is converted and prepare a branch with the ghosts filled [01:34] stub or I have to do the actual merge of data into rocketfuel itself [01:35] plus I'll need to write a bzr script to refresh all the annotation data in rocketfuel itself, which is needed to get the right answers to bzr annotate [01:35] btw, right now you should get useful answers to annotate, just not complete ones - it will show the merged revision in the mainline [01:35] which you can see who it came from easily [01:35] wasn't so useful [01:36] I got lots of "pqm@.... " and only a few actual names [01:36] quite a few blank lines too [01:36] can I ask you chat with spiv / jamesh / me next time you try to do this [01:36] as it may be a UI issue [01:36] ok [01:36] I was chatting with mpool last time, btw [01:37] and I think he identified a UI issue from it [01:37] Is it gramtically correct to say something like "May contain lowered case letters, numbers, and dashes only..." [01:37] but I don't recall the details [01:37]