[12:16] SteveA: possible, but I got mail from it, a couple of hours ago [12:17] me too, but not 10 mins ago [12:17] it's normally very responsivle [12:17] next note to self, don't do ls in the wiki.u.c user dir [12:18] I'm probably too tired to be doing this too :/ [12:18] SteveA: I'll check in a sec [12:18] heh [12:21] mdke: done [12:21] fanks [12:22] elmo: it's arrived [12:23] SteveA: ok, just confirmed esperanza is swamped again - we have an upgrade scheduled to help with that, but I suspect eventually I'm going to have to do something more drastic like move internal lists to a new server (launchpad-error-reports is particuarly hurtful with mailman) [12:24] one day someone will write a better mailman [12:25] SteveA: btw, we should talk tomorrow quickly about beta === coNP [n=conp@pool-00a7b.externet.hu] has left #launchpad ["c-x] === jelmer [n=jelmer@a62-251-123-16.adsl.xs4all.nl] has joined #launchpad [12:37] elmo: we'll be toning down launchpad-error-reports pretty soon [12:37] SteveA: excellent [12:37] and replacing a lot of the traffic there by either nothing, or librarian files, or oops reports [12:37] it will remain just for when scripts totally fail [12:37] what do we need to talk about concerning beta? [12:38] it seems a bit slow to me [12:38] even though stu keeps saying it isn't [12:40] SteveA: I'll ping you tomorrow about the NlSprint [12:40] ok [12:42] SteveA: that's what we need to talk about - the speed ;-) [12:43] oh [12:43] so, I don't know if the new ui is intrinsically slower [12:43] or if it's time spent loading graphics and JS etc. [12:43] or it's a slow app server machine [12:43] I can look into it using firebug [12:43] well, I'm fairly sure having it on asuka isn't helping [12:43] ok [12:44] it's an app server machine a) doing other things and b) doubling as (many) database servers [12:44] ok [12:44] so, let's not run it there [12:44] so I'd like to move it to carbon [12:44] +1 from me [12:44] provided we don't need to randomly take carbon down [12:44] well when I say "I", I mean, I'd like the DBAs too ;-) but wanted to check with you first [12:44] we'd only take carbon down if jubany was down === dfarning [n=dfarning@207-118-209-185.dyn.centurytel.net] has joined #launchpad [12:44] which I think is something we can live with [12:44] (and by down, I mean down with smoking hardware) [12:44] I've been kind of asking stu to move it to something like carbon for a couple of weeks [12:45] so, I'm very much in favour [12:45] ok, cool, thanks [12:45] and it should happen as soon as possible [12:45] New bug: #81380 in malone "Encrypted file extensions inconsistent" [Undecided,Unconfirmed] https://launchpad.net/bugs/81380 === SteveA --> sleeping [12:46] Hey guys I am interested in have all of the bugs for a lauchpad team sent to our -bugs mailing list [12:48] the team is mozillateam and the mailing list is ubuntu-mozillateam-bugs [12:48] can't you just set the bug contact as the mailing list address? [12:49] I'll go check [12:49] actually I guess it's better to make a user for the mailing list and add it to the team [12:50] or subscribe it to the package, or whatever [12:53] That makes sense. I'll create a mozillateam-list user who is whos mail is sent to the list. Thanks [12:53] sorta like how Ubugtu works [12:55] New bug: #81384 in launchpad-bazaar "Report status (e.g. "initial upload in progress") of pushes to hosted branches in web UI for a branch" [Wishlist,Unconfirmed] https://launchpad.net/bugs/81384 === dfarning [n=dfarning@207-118-209-185.dyn.centurytel.net] has left #launchpad [] === WebMaven_ [n=webmaven@ip72-193-220-34.lv.lv.cox.net] has joined #launchpad === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #launchpad [01:45] New bug: #81391 in launchpad "Order of milestone list when editing bug details should be chronological instead of alphabetic" [Undecided,Unconfirmed] https://launchpad.net/bugs/81391 === jinty [n=jinty@111.Red-83-49-48.dynamicIP.rima-tde.net] has joined #launchpad [02:21] New bug: #81394 in launchpad-support-tracker "Passing a list to the search tickets view crashes" [Undecided,Confirmed] https://launchpad.net/bugs/81394 [02:36] New bug: #81395 in Ubuntu "boot process interrupted by "could not kill pid 1984"" [Undecided,Unconfirmed] https://launchpad.net/bugs/81395 === jinty [n=jinty@64.Red-83-50-216.dynamicIP.rima-tde.net] has joined #launchpad === Bhaskar [n=Bhaskar@202.79.37.177] has joined #launchpad === sfllaw [i=sfllaw@debian/developer/coleSLAW] has joined #launchpad === Trickser [n=sergio@p54A5C918.dip.t-dialin.net] has joined #launchpad === Seveas [n=seveas@ubuntu/member/seveas] has joined #launchpad === netjoined: irc.freenode.net -> anthony.freenode.net === quail [n=quail@unaffiliated/quaillinux/x-000001] has joined #launchpad === poolie [n=mbp@intern182.lnk.telstra.net] has joined #launchpad === marcus_notebook [n=mholthau@67.173.79.83.cust.bluewin.ch] has joined #launchpad === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === mdz [n=mdz@scandic759.host.songnetworks.se] has joined #launchpad === shawn___ [n=shawn@netblock-68-183-69-197.dslextreme.com] has joined #launchpad === carlos [n=carlos@168.Red-88-17-199.staticIP.rima-tde.net] has joined #launchpad [09:08] morning [09:13] Is there anyone around who could talk me step-by-step through the process of pushing a repository to my userspace? [09:14] Or, I suppose, point me to a webpage doing that. === raphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === matthewrevell [n=matthew@77-98-66-72.cable.ubr05.wolv.blueyonder.co.uk] has joined #launchpad === jinty [n=jinty@64.Red-83-50-216.dynamicIP.rima-tde.net] has joined #launchpad === mdz [n=mdz@scandic759.host.songnetworks.se] has joined #launchpad === doko [n=doko@scandic759.host.songnetworks.se] has joined #launchpad === seb128 [n=seb@scandic759.host.songnetworks.se] has joined #launchpad === jelmer [n=jelmer@a62-251-123-16.adsl.xs4all.nl] has joined #launchpad [10:00] New bug: #81419 in launchpad-support-tracker "translate mail and web messages for l10n support" [Undecided,Unconfirmed] https://launchpad.net/bugs/81419 === rraphink [n=raphink@ubuntu/member/raphink] has joined #launchpad [10:05] New bug: #53292 in launchpad-support-tracker "Create/follow support requests through a mailing list" [Wishlist,Confirmed] https://launchpad.net/bugs/53292 === Hobbsee [n=Hobbsee@ubuntu/member/hobbsee] has joined #launchpad === mpt yawns [10:50] New bug: #81433 in update-manager "Error to install package vim in upgrade to Fiety using update-manager" [Undecided,Unconfirmed] https://launchpad.net/bugs/81433 === rraphink [n=raphink@ubuntu/member/raphink] has joined #launchpad === matthewrevell_ [n=matthew@77-98-66-72.cable.ubr05.wolv.blueyonder.co.uk] has joined #launchpad === mdz [n=mdz@scandic759.host.songnetworks.se] has joined #launchpad === fabbione [n=fabbione@vpn-nat.fabbione.net] has joined #launchpad === Gwaihir [n=Gwaihir@mail.foredil.it] has joined #launchpad === matthewrevell__ [n=matthew@77-98-66-72.cable.ubr05.wolv.blueyonder.co.uk] has joined #launchpad === matthewrevell [n=matthew@77-98-66-72.cable.ubr05.wolv.blueyonder.co.uk] has joined #launchpad === BjornT [n=bjorn@clt-84-32-240-183.dtiltas.lt] has joined #launchpad === jelmer [n=jelmer@a62-251-123-16.adsl.xs4all.nl] has joined #launchpad === cprov-afk is now known as cprov [12:01] good morning ! [12:03] cprov: morning :) [12:06] good morningn! [12:07] gotten morgan === Hobbsee waves === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad === niemeyer [n=niemeyer@201.11.214.142] has joined #launchpad === mdz [n=mdz@195.159.8.179] has joined #launchpad === niemeyer [n=niemeyer@201.11.214.142] has joined #launchpad === salgado [n=salgado@200-171-140-32.dsl.telesp.net.br] has joined #launchpad [12:53] meeting in 6 mins [12:53] 7 [12:58] kiko's script has gotten smart === flacoste [n=francis@modemcable207.210-200-24.mc.videotron.ca] has joined #launchpad [12:59] except it thinks 6.4 is 7 [01:00] so [01:00] kiko-fud: hello ;-) [01:00] Welcome to this week's Launchpad development meeting. [01:00] who is here today? [01:00] me [01:00] me [01:00] jamesh sends apologies. I have his three sentences. [01:00] me [01:00] me [01:00] me [01:00] * BjornT: Will be at the distro sprint in Oslo. [01:00] * Matsubara: Vacation. [01:00] * Andrew: at sprint [01:00] me [01:01] me [01:01] me [01:02] [01:02] == Agenda == [01:02] * Roll call [01:02] * Agenda [01:02] * Next meeting [01:02] * Activity reports [01:02] * Actions from last meeting [01:02] * Oops report (Matsubara) [01:02] * Bug report (mpt) [01:02] * Bug tags [01:02] * Production and staging (Stuart) [01:02] * Launchpad 1.0 status reports [01:02] * Sysadmin requests [01:02] ---- [01:02] me [01:02] * A top user-affecting issue (MatthewRevell) [01:02] * Everyone to comment "fixed in RF ''revision''" when marking a bug as Fix Committed (mpt) [01:02] * Progress of UI week (Kiko/Steve) [01:02] * MOTU bugs (Kiko) === WaterSevenUb [n=WaterSev@242-87.dial.nortenet.pt] has joined #launchpad [01:02] * (other items) [01:02] ---- [01:02] * Three sentences [01:02] === kiko-fud is now known as kiko [01:02] Next meeting, same time next week [01:02] Activity reports. [01:02] I'm still slack... [01:02] from last week: [01:02] * kiko: "I didn't do mine this week" [01:03] * salgado [01:03] * cprov: "I suck, 1 week behind" [01:03] kiko-fud: has caught up this week [01:03] I didn't do mine this week either, but I could [01:03] no I haven't [01:03] up to date [01:03] up to date [01:03] up to date [01:03] up to date [01:03] up td date [01:03] I suck, a few days behind [01:03] I sent a summary for last week and this week I'm almost up to date (missing yesterday's only) [01:03] not I haven't caught up properly, still suck [01:04] as usual, sprinters are excused of sending activity reports [01:04] although it's still nice if they want to [01:05] is that everyone? [01:05] * Actions from last meeting [01:06] apparently, there were none [01:06] * Oops report (Matsubara) [01:06] matsubara is away. is someone doing this for matsubara? [01:06] so I'm a bit embarassed but I didn't get anything from matsubara, even though he said he would do it yesterday [01:06] did he contact anyone else? [01:06] guess not [01:07] ok. kiko would you arrange something and mail the list later? [01:07] yes. the OOPSes are down from last week fwiw [01:07] everyone, please look out for an oops-realted email from kiko, and respond to any items specifically for you on there [01:07] * Bug report (mpt) [01:08] thanks kiko [01:08] There are 14 known Critical bugs in Launchpad without released fixes. The oldest six are: [01:08] * Bug #30602 (Timeout errors in +translate), Critical, In Progress, kiko [01:08] Malone bug 30602 in rosetta "Timeout errors in +translate" [Critical,In progress] https://launchpad.net/bugs/30602 - Assigned to Christian Reis (kiko) [01:08] up to date [01:08] kiko, any progress this week? [01:08] * Bug #46982 (Need to support KDE like plural forms), Critical, Confirmed, danilo [01:08] Malone bug 46982 in rosetta "Need to support KDE like plural forms" [Critical,Confirmed] https://launchpad.net/bugs/46982 - Assigned to (danilo) [01:08] danilo, how's this doing? [01:08] * Bug #49989 (branch puller reports failure for new hosted branches), Critical, Confirmed, spiv [01:08] Malone bug 49989 in launchpad-bazaar "branch puller reports failure for new hosted branches" [Critical,Confirmed] https://launchpad.net/bugs/49989 - Assigned to Andrew Bennetts (spiv) [01:09] mpt: no work on ff, so no work on this one this week [01:09] spiv, this is newly Critical. Will it soon become newly fixed? :-) [01:09] danilos, "ff"? === mpt is slow today [01:09] mpt: firefox import/export support [01:09] oh, you were working on ff instead [01:09] ok [01:09] * Bug #68295 (private), Critical, Confirmed, salgado [01:09] Bug 68295 on http://launchpad.net/bugs/68295 is private [01:10] salgado, will you have time for that in the coming week? [01:10] ddaa: please get to this meeting on time in future [01:10] sorry [01:10] kiko? spiv? [01:10] ddaa: can you comment on bug 44989? [01:10] Malone bug 44989 in cupsys "Doesn't print (large) PDF files" [Medium,Confirmed] https://launchpad.net/bugs/44989 [01:10] mpt, it's fixed already. I'm going to land the fix today [01:10] um [01:10] mpt: bug #46982 is blocked on Firefox, that's why it's not yet started [01:10] ddaa: can you comment on bug 49989? [01:10] * Bug #74839 (private), Critical, Confirmed, mpt [01:10] I have not made any progress on this this week. Action for me for next week: Either fix it, or talk with SteveA about how else it can be fixed. [01:10] Bug 74839 on http://launchpad.net/bugs/74839 is private [01:11] SteveA: hu? "Dropdown menus in 1.0 UI do not drop down" ? [01:11] carlos: what does "blocked on Firefox" mean exactly? [01:11] mpt, I have a branch now and am looking at this [01:11] SteveA, on the firefox work. [01:11] hu no... [01:11] kiko, that's great news [01:11] * Bug #75333 (Restrict pockets that upload translations into Rosetta), Critical, Fix Committed, carlos [01:11] Malone bug 75333 in rosetta "Restrict pockets that upload translations into Rosetta" [Critical,Fix committed] https://launchpad.net/bugs/75333 - Assigned to Carlos Perell Marn (carlos) [01:11] SteveA: we need infrastructure added by the Firefox branch [01:11] carlos, did this deserve a cherry-pick? [01:11] there will be a full roll out early next week [01:12] SteveA: it's a couple hours fix with my ff-branch [01:12] ah, spiv isn't here [01:12] mpt: yes, and I think I did it already (the request) [01:12] no such bug as 49989 [01:12] so, write email to stuart cc list to organise getting important stuff rolled out [01:12] be organised about this [01:12] carlos, ok, thanks. [01:12] so it will be smooth [01:12] That's all, thanks SteveA === TeTeT [n=spindler@modemcable178.77-70-69.static.videotron.ca] has joined #launchpad [01:12] SteveA: when is stub back from vacation [01:12] sorry outdate bookmark [01:12] mpt: confirmed, I did it [01:12] danilos: monday [01:12] mpt: I'd also like to have bug 81278 cherrypicked [01:12] Malone bug 81278 in rosetta "Rosetta PO export is broken" [Critical,Fix committed] https://launchpad.net/bugs/81278 - Assigned to (danilo) [01:12] On bug 49989, spiv reports he's very much working on it. [01:13] danilos, you've made the necessary wiki page changes? [01:13] danilos: so, mail stuart, cc list today about organising what you need rolled out [01:13] ddaa, cool. [01:13] as seen in his latest emails in "supermirror latency" discussion. [01:13] it's on the wiki page, PO exports are broken because this is still waiting [01:13] SteveA, well, we could ask lifeless to cherrypick it [01:13] lifeless seemed to be too busy with sprint yesterday [01:13] no point as we'll be doing a rollout early next week [01:13] and there is plently of ui 1.0 work for people to do [01:13] * Bug tags [01:14] just fif-candidate [01:14] we discussed this last week, and I think we agreed to decline it [01:14] +1 [01:14] because just tagging as fix-it-friday should work well enough [01:15] except if matthewrevell offers reasonable background [01:15] any comments on that matthewrevell ? do you disagree strongly? [01:15] SteveA: I don't disagree, no. [01:15] what does a fix-it-friday tag means? does it only mean that a bug is a candidate? [01:15] ok, so, it's declined [01:15] SteveA: It was more Matsubara's suggestion, though, so I don't want to speak in his stead. [01:15] I mean, should we remove the fix-it-friday tag once the bug is fixed? [01:15] salgado: https://help.launchpad.net/TaggingLaunchpadBugs [01:15] read the description there [01:16] SteveA, so.. [01:16] if the description there is not clear enough, then ask for clarification here. if the description there does not match what we actually do [01:16] the fif-candidate was meant to be a workflow tag to help matsubara and matthewrevell coordinate [01:16] I'm asking because I had this discussion with matthewrevell [01:16] then ask matthewrevell to change its meaning [01:16] matsubara had built a page with a list of bugs [01:16] I asked him why are you doing this? [01:16] he said: how else could I group bugs that are potential fifs? [01:16] I said use a tag. [01:16] that's how it started [01:16] well [01:17] now, we could soften the meaning of the main f-i-f tag [01:17] why not mark potential fif bugs as fix-it-friday [01:17] right [01:17] we could do that [01:17] and get them assigned to people when they're actually gong to be done [01:17] sounds fine by me [01:17] SteveA++ [01:17] matthewrevell? [01:17] SteveA, that's why I asked for an explanation. I wanted to make sure that it _only_ means that a bug is a good candidate [01:17] cool, sounds good [01:17] SteveA: +1 [01:17] in fact, I'm doing it already... (only with two bugs) [01:17] Equivalent of "gnome-love" in b.g.o or "helpwanted" in b.m.o [01:17] mpt, no... helpwanted is something else [01:17] (roughly) [01:17] ok. matthewrevell please put the fif-candidate tag into the declined tags with a reason, and clarify the description of fix-it-friday [01:18] on the tags page [01:18] ok [01:18] mpt, and helpwanted couldn't make sense for launchpad really :-P [01:18] yeah [01:18] that's a MeetingAction, btw [01:18] but it sorta means "this is easy enough for anyone to do" [01:18] * Production and staging (Stuart) [01:18] stuart isn't here [01:18] I have some things to say [01:18] a database patch landed on mainline [01:19] when it was meant to be closed to database changes [01:19] so edge isn't updating [01:19] and we can't get newer changes from mainline to the ui branch [01:19] until we do a rollout [01:19] I'm going to get stuart/lifeless to add an actual switch to pqm [01:19] SteveA: is that my security.cfg change, or something else? [01:19] to forbid database landings when we're in a freeze [01:19] duh [01:19] as this is becoming an important part of our workflow [01:20] anyway, the tree is open to database landings now [01:20] danilos: nop, was my DB patch-67-14 ... [01:20] so, if you have previously approved database patches, land them now [01:20] it should still be possible to do backwards compatible database patches... [01:20] cprov: ah, ok, thanks; so security.cfg should not be a problem? [01:20] when stub is back, we'll arrange a rollout, and sync up edge and beta again [01:20] danilos: it should [01:20] too much workflow, too much workflow... [01:20] ddaa: do you have something positive to contribute here? [01:21] it should still be possible to do backwards compatible database patches... [01:21] ddaa: do not arrive late, and also just be negative in the meeting [01:21] danilos: I think it's *also* a problem. [01:21] cprov: ok, I'll be careful with them as well [01:21] I'm not deing negative, I'm saying that refusing all database patches is excessive in my opinion [01:21] ... for the record. [01:21] ddaa: I will explain edge to you later, after the meeting [01:21] There could be a window of ~2 days before each rollout where they could be allowed [01:21] ddaa: that kind of patches can be handled by Stuart directly [01:22] SteveA, well, let's see what ddaa has as an alternative? [01:22] kiko: yes, after the meeting [01:22] ddaa, do you have an alternative to rejecting database patches that stills keeps edge running? [01:22] kiko, ddaa: after the meeting [01:22] SteveA, don't give him a railing and not let him explain himself [01:22] because that would hardly block edge [01:22] kiko: pqm checking that mainline can run with production schema. [01:22] kiko: he should have done that when he was complaining. [01:23] so, to conclude production and staging... write email to stuart, cc list [01:23] to coordinate any rollouts you need to have done [01:23] and any database landings you need [01:23] ddaa, I didn't understand what you meant. [01:23] do it today [01:23] so that you're not doing it during FiF, and so stuart gets the email as soon as he gets back [01:24] we'll coordinate a full rollout early next week [01:24] then edge will work again [01:24] * Launchpad 1.0 status reports [01:24] Rosetta 1.0 weekly report: [01:24] - firefox import/export: no progress this week [01:24] - oo import/export: no progress this week [01:24] - translation review: DONE [01:24] - essential docs: no progress this week [01:24] - search via translation browsing: DONE [01:24] - checks not to upload wrong language PO file using "too many changes" check: Pending final spec discussion [01:24] - translation page for projects: bug 73875 (implemented, waiting for review), bug 79674 (in progress) [01:24] Malone bug 73875 in rosetta "Project needs a Translations page" [High,In progress] https://launchpad.net/bugs/73875 - Assigned to Carlos Perell Marn (carlos) [01:24] Malone bug 79674 in rosetta "List translatable upstreams on separate page, sample on front page" [High,In progress] https://launchpad.net/bugs/79674 - Assigned to (danilo) [01:24] UI 1.0 report: [01:24] * Remaining graphics arrived, not landed yet. [01:24] * Many priority-2 pages implemented, and global search hooked up. [01:24] = Soyuz-1.0 Report = [01:24] * Archive Rework: tested SoyuzTestSystem, pending code review [01:24] * KeyServer DoS: fixed with a dedicated internal KeyServer for Soyuz. [01:24] * ClosingBugsFromChangelog: discussion & prototype strategy definition [01:24] * Incoming Fixes: [01:24] * #76591 (Reliable PackageRelationShip parser/render): [01:24] merge-conditional (cprov, r=spiv) [01:25] * #74965 (failure on +queue page permission check for empty queues): [01:25] pending-review (cprov, r=jamesh) [01:25] * #59443 (do not announce uploads to BACKPORTS): [01:25] pending-review (cprov, r=jamesh) [01:25] - PillarGotchis: going to land today [01:25] = Support^WAnswer Tracker 1.0 = [01:25] * SupportTrackerRename: spec in review, waiting for sanity check by SteveA. [01:26] ddaa, I /think/ I understood what you meant. but that would probably never happen [01:26] thank you everyone [01:26] * Sysadmin requests [01:26] - there is an RT request about making the new bazaar code browser visible to the outside world [01:26] I'm very keen on seeing that work [01:27] anything else? [01:27] 6 [01:27] 5 [01:27] 4 [01:27] 3 [01:27] 2 [01:27] 1 [01:27] ok [01:27] * A top user-affecting issue (MatthewRevell) [01:27] all my requests were dealt with promptly -- go elmo + Znarl + sysadmins [01:27] This week's user-visible issue has obviously been the broken PO file exports. [01:27] I've created a spec that I believe will help us better communicate about similar issues: [01:27] https://blueprints.launchpad.net/launchpad/+spec/system-status-page [01:27] Basically, it's a system status page, similar to that provided by ISPs. I think it will boost user confidence, because they'll see we're aware of issues and working ona fix. Your feedback, or cries of "we've spoken about it and decided it's a bad idea because xxx", will be greatly appreciated. [01:27] Through a cruel key-combination, I managed to close Firefox whilst typing the spec page into the wiki, so I'll have to re-type it after the meeting. [01:27] excellent feedback kiko [01:28] matthewrevell: nice idea [01:28] bad key fumble though [01:29] kiko: I shouted very loudly [01:29] :) [01:29] matthewrevell: I like the sound of this. Please mail the launchpad list when you have the retyped spec in there. [01:29] SteveA: will do [01:29] * Everyone to comment "fixed in RF ''revision''" when marking a bug as Fix Committed (mpt) [01:29] The consensus from the discussion about "how do we tell what revision a bug is fixed in" seemed to be that: [01:29] matthewrevell: have you took the opportunity to switch to epiphany? the idea seems great, though [01:29] When you mark a bug Fix Committed, in the bug report you should comment the revision it was fixed in, e.g. "fixed in RF 456789". [01:29] So, this is just a reminder for everyone to do that. [01:29] That's all. :-) [01:29] thanks mpt [01:29] I have a further suggestion [01:30] let's agree on a standard way to say this [01:30] so when we have private branches and the code browser [01:30] we can make it a hyperlink [01:30] or even before then [01:30] (And so that later if we have a "fixed in" field, it can slurp up our comments...) [01:30] we can automate, right, that would be great [01:30] we can make it a link for lp developers to a codebrowser on devpad [01:31] I would *love* a link to a codebrowser from the bug :) [01:31] I know of the discussion of marking bugs as fixed in Ubuntu package changelogs; has anyone considered that for LP as well with our pqm-submit messages? [01:31] ddaa: the revision number in rocketfuel... is it unique to a particular branch? or to the whole repository? [01:31] I'd suggest %s{unique_name}@%d{revno} [01:31] (iow, making this two-way) [01:31] like, if we're working on beta and on mainline, those are different revno sequences I think [01:31] SteveA: revision number is only meaningful in a branch [01:31] ok, thanks ddaa [01:32] so, we need to have something like what ddaa suggested [01:32] SteveA: if you want repository meaningful, you need the revision id [01:32] and not just RF [01:32] rev id is too long [01:32] SteveA, it's easy to cut-n-paste though [01:32] in the context of a launchpad bug, "mainline 3345" might work, "beta 6666" [01:33] anyway, let's take this to the list or discussion later [01:33] but revid would work for other projects using bzr as well [01:33] thanks mpt [01:33] * Progress of UI week (Kiko/Steve) === ddaa has some more ideas using product.development_focus and series.branch [01:33] I want to do a quick poll [01:34] if you did some work that directly improved the 1.0 ui this week say "I improved it". If you did not, say "I didn't improve it (yet)" [01:34] I didn't improve it (yet) [01:34] I improved it [01:34] I improved it [01:34] I improved it [01:34] I didn't improve it (yet) [01:34] I didn't improve it (yet) [01:34]