/srv/irclogs.ubuntu.com/2009/09/23/#launchpad-meeting.txt

=== Ursinha is now known as Ursinha-afk
=== mrevell-dinner is now known as mrevell
=== danilo-afk is now known as danilos
=== cprov-afk is now known as cprov
=== mrevell is now known as mrevell-lunch
=== Ursinha-afk is now known as Ursinha
=== mrevell-lunch is now known as mrevell
barry#startmeeting15:01
MootBotMeeting started at 09:01. The chair is barry.15:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:01
barryhi everyone and welcome to this week's ameu reviewers meeting.  who's here today?15:01
danilosme15:01
bigjoolsme15:01
barrywow15:02
bigjoolseveryone must be busy with something else, can't think what15:02
intellectronicame15:03
barryintellectronica, gary_poster cprov salgado sinzui noodles775 jml allenap EdwinGrubbs rockstar bac ping15:03
noodles775me15:03
jmlhi15:03
cprovme15:03
salgadome15:03
bacbarry: apologies15:03
gary_posterme15:03
barryno worries15:03
barry[TOPIC] agenda15:03
MootBotNew Topic:  agenda15:03
barry * Roll call15:04
barry * Action items15:04
barry * UI review call update15:04
barry * Linked artifacts (e.g. screenshots) from bugs and merge proposals should not disappear [bac]15:04
barry * Peanut gallery (anything not on the agenda)15:04
barry 15:04
barry 15:04
barry[TOPIC] * Action items15:04
MootBotNew Topic:  * Action items15:04
barry * gary_poster and barry will transfer review guidelines from the old wiki and old old wiki to the new wiki15:04
barrypostponed until after 3.015:04
gary_posterbah :-)15:04
EdwinGrubbsme15:04
barry * cprov to update guidelines to clarify how code sensitive to env changes should be written15:04
cprovbarry: shhh, sorry again15:04
barrycprov: no worries15:05
barry[TOPIC]  * UI review call update15:05
MootBotNew Topic:   * UI review call update15:05
barrybeuno: hi!  would you like to say a few words here?15:05
flacosteme15:06
bigjoolsdoesn't look like it :)15:06
barryit doesn't ;)15:07
barryanyway...15:07
henningeme ;)15:07
barry[TOPIC]  * Linked artifacts (e.g. screenshots) from bugs and merge proposals should not disappear [bac]15:07
MootBotNew Topic:   * Linked artifacts (e.g. screenshots) from bugs and merge proposals should not disappear [bac]15:07
bachi15:07
beunobarry, hi15:07
beunome15:07
bacdoing QA i found screenshot links where the item was no longer there.  very frustrating.  that is all.15:07
beunoI love you guys15:07
barrybeuno: :)15:08
beunoand you've done an amazing job at 3.015:08
intellectronicabac: best to always use an upload, then?15:08
beunoUI reviews went so well, I want them to be done everywhere else15:08
bacintellectronica: probably.  or just don't prematurely purge on rookery.15:08
barrybac: agreed!  i would also strongly urge people to file a bug, link that bug to your branch, and include demo/qa plan in your cover letter.  as i'm qa'ing things this week i find it very difficult when those things are missing15:09
barrybeuno: things are looking good, are they not? :)15:09
jmlalso, we should allow attachments on merge proposals.15:09
beunobarry, yes. There are a few "critical" issues on major pages15:10
barryjml: +115:10
beunolike the bug page, mps and branch index15:10
beunosome of them have been addressed15:10
beunoand some of them, we won't have time15:10
beunolesson of the day:  don't levae the biggest pages last15:10
jmlwhich, of course, means that the merge proposals page should use the same attachment infrastructure as bugs.15:10
barrybeuno: we're going to have to cp them after the release15:11
barrybac has basically said "keep qa'ing but if you find something, it's too late now"15:11
intellectronicajml: there are various opportunities to share infrastructure that we should consider now15:11
beunobarry, right, it's fixable15:11
beunoin general, it's an awesome launchpad15:11
beunoall tempaltes have been converted15:11
* barry is just amazed we actually converted all 375 templates15:11
beunoeven with me sneaking away for 2 weeks15:12
jmlbarry, me too!15:12
beunoyou guys rocked the house15:12
jmlintellectronica, very much so. MPs already use bugs comment infrastructure, largely.15:12
barrybeuno: can we do a post-mortem after 3.0 is released, and maybe when you're done sprinting, etc. to evaluate the 3.0 process?  and also to think about what needs to be done post-3.0 and what's on the plate for 4.0?15:13
barrybeuno: it would be great to evaluate what we just did before we leap headfirst into 4.015:13
beunobarry, absolutely15:14
barrygreat!15:15
barry[TOPIC] peanut gallery15:15
MootBotNew Topic:  peanut gallery15:15
barrythat's everything on the agenda, does anybody else have anything for today?15:15
flacostebarry, beuno: we are putting a 3.0 retrospective at the TL meeting15:16
jmlbarry, nope.15:16
beunoflacoste, perfect15:16
barryjml: i think you're right, so...15:16
barry#endmeeting15:16
MootBotMeeting finished at 09:16.15:16
flacostebarry: ideally, TL would be able to do a retrospective with their team15:16
flacostebefore then15:16
barrythanks everyone and have a happy qa day15:16
flacostebut i'm not sure it's practical15:16
barryflacoste: isn't the tl next week?15:17
flacostebarry: it is15:17
flacostebut sinzui is sprinting this week for example15:17
flacostethe southern hemisphere has basically a day less in this week15:18
flacosteetc.15:18
flacostewe are releasing15:18
barryflacoste: exactly :)15:18
barryanyway... see you back at the ranch15:18
=== ursula_ is now known as Ursinha
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== mrevell is now known as mrevell-dinner
=== Ursinha is now known as Ursinha-brb
=== danilos is now known as danilos-afk
=== mrevell-dinner is now known as mrevell
=== Ursinha-brb is now known as Ursinha
barry#startmeeting23:30
MootBotMeeting started at 17:30. The chair is barry.23:30
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]23:30
barryhello and welcome to this week's asiapac reviewers meeting.  who's here today?23:30
mwhudsoni am!23:30
thumperhey23:30
wgrantmoi23:30
thumperbarry: rockstar may be lying down23:30
barryexcellent23:31
barrythumper: cool23:31
barrythumper, mwhudson y'know your evil plan to increase the number of antipodeans is backfiring23:31
thumperwhy?23:31
barryjml23:31
barry;)23:32
barryanyway...23:32
barrynot much happened in ameu23:32
mwhudsonthe plan hadn't really got far enough that you could call it evil...23:32
barrybac requested that folks keep their screen shots around long enough to do qa.  some screen shots were not attached to the bug, but instead were on rookery, and got deleted23:33
thumperI'd like to be able to add attachments to a code review23:33
barryit's recommended to attach them to the bug, or at least keep them around until the end of the cycle23:33
barrythumper: that came up too23:33
* thumper adds it to the wish list23:33
thumperbarry: you can attach them to the mail23:33
thumperbarry: and we could link them on the UI23:34
bacbarry:  you woke me up for that?  lies back down to monitor the release23:34
barrythumper: yep!23:34
thumperbarry: the images are stored in the librarian (I think)23:34
thumperbarry: I'll test23:34
barrycool, thanks23:34
thumperperhaps not today23:34
barrythumper: in the original mp request is probably the most important23:35
barrythe only other thing from ameu is: lp 3.0 is awesome and beuno loves you23:35
barrythat's all i have.  what's up with you?23:35
wgrantI can no longer complain about the lack of public ec2test.23:36
barrywgrant: we have that now?23:37
mwhudsonwell, he does23:37
mwhudsonit's not actually 'public' yet23:37
barrymwhudson: cool23:37
mwhudsonbecause i need to land ec2test changes23:37
thumperI don't have anything review specific to bring up23:37
mwhudsoni guess we could mention that review diffs will be a bit different post rollout?23:38
thumperperhaps23:38
barrymwhudson: how so?23:38
thumperpushing will cause the diff to be updated23:38
mwhudsonthey'll update on push23:38
mwhudsonand they're merge --preview diffs, not diff -r ancestor: diffs23:38
mwhudson(so you can get conflicts)23:38
mwhudsonthumper: are the old diffs kept around?23:39
thumperkinda23:39
thumpernot really23:39
thumperyet23:39
barryupdates are nice23:39
mwhudsonthumper: there was this idea of linking a code review comment to the diff it applied to, i guess that's not done yet?23:39
thumperthere is23:39
thumperbut that is a db patch23:39
mwhudsonright23:39
barrymwhudson: what's the reason behind the merge --preview diffs?  to be explicit about conflicts?23:39
thumperthat is the only way we can get reasonable diffs23:40
thumperbarry: because if you merge the target23:40
mwhudsonbarry: conflictyness seems interesting to the reviewer23:40
thumperbarry: you don't want the merged details in the diff23:40
barrythanks.  how does this affect support for dependent branches?23:41
mwhudsonanother thing, jml has this half-written branch that will pull all the details for an ec2 test run from the merge proposal23:41
thumperheh23:41
thumperwell23:41
thumperright now they aren't really supported23:41
thumperabentley is working on fixing the dependant branch support23:41
thumperbeing renamed to "prerequisite branch"23:41
mwhudsonwhich i think will be a useful improvement23:41
thumpermwhudson: including commit message?23:42
mwhudsonthumper: i presume so23:42
barrymwhudson: where useful == awesome23:42
thumperbarry: part of this would be to get LP to somehow work well with pipes23:42
thumperbarry: have you used bzr-pipelines yet?23:42
thumperbarry: IMO if you like looms, you'll love pipelines23:43
barrythumper: i keep meaning to.  i know they are the official goodness to use instead of looms23:43
thumperbarry: they just work better with LP as they are branch based23:43
barryhonestly though, i haven't had many branch stacks during these last two cycles23:43
thumper:)23:43
jmlincluding commit message.23:43
jmlit assembles the [r=...] gunk from the mp23:44
jmland takes the actual text of the commit message from the mp too23:44
jml(but iirc, you can override it)23:44
barryjml: my last commit message is usually meaningless, e.g. 'pick some lint' or 'merge rf'23:44
thumperbarry: the proposal has a commit message field23:44
thumperbarry: not set very often right now. tarmac uses it23:45
barryi'll have to start using that.  i've basically ignored the Subject: field until now23:45
barrybut it all sounds cool23:45
thumperbarry: it isn't the subject23:45
barrythumper: isn't that last commit message stuffed into the subject in a 'bzr send'?  or is that something else?23:45
thumperbarry: we don't do anything with that subject23:46
barrythumper: that's why i've started to ignore it23:46
thumperbarry: but the commit message is a different bit23:46
barryi have one other thing i'd like to ask y'all23:47
thumpershoot23:48
barryis this time still the best for the asiapac meetings?23:48
thumperstill good for me23:48
thumperalthough we change next week23:48
thumperdaylight savings kicks in23:48
* thumper thinks23:48
thumperso becomes one hour later23:48
barrypersonally, i wouldn't mind moving it earlier by an hour (or more) but i want to make sure we continue to meet at a good time for you23:48
thumperI'm fine with this time23:49
barrythumper: you just blew my mind23:49
thumpercould be fine an hour earlier too as of next week23:49
barryso that means 2130 utc?23:49
thumpermwhudson: got any preference?23:49
thumperbarry: yes23:49
* mwhudson blinks his attention back, sorry about that23:50
mwhudson2130 utc next week is 0930 local?23:50
mwhudsonthat's fine with me23:50
barryi'll probably bitch and moan again by 01-nov when we fall out of daylight savings, but for now that would be great23:50
thumpermwhudson: 2130 utc next week is 1030 local23:50
thumpermwhudson: daylight savings sunday23:51
mwhudsonoh right23:51
mwhudsonthat's completely fine23:51
barrygreat!  2130 it is23:51
barrythat's all for me23:51
mwhudsonanother hour earlier would be ok, though risks bumping into our standup23:51
thumperbarry: well, in nov it would be another hour earlier for you23:51
thumperbarry: which would make it what?23:51
mwhudsonan hour earlier than that would be ok, though that's getting a little early here (0830)23:51
barrythumper: i think it would make it 1630 for me which would be perfect23:52
thumpermwhudson: I was talking about US going out of daylight savings23:52
mwhudsonthumper: i'm just being general23:52
mwhudsonthumper: now jml is off, we can go earlier, is the basic summary23:52
thumperright23:52
barryright23:52
thumperwe could do 20:30 utc23:53
barry2130 should be fine now and after 01-nov23:53
barryif not, it's good to know we can push it a bit, but probably not necessary23:53
barryanyway...23:53
barryanything else guys?23:53
thumperwhat about 2100 ?23:53
thumperbarry: it used to collide withour standup23:54
thumperbarry: but we moved that23:54
barrythumper: ah cool.  2100 is fine too23:54
thumpermwhudson: 2100?23:54
mwhudsonthumper: yes, fine23:54
thumperbarry, mwhudson: sold!23:54
barrybeauty23:54
barrythanks guys... i think we're done!23:55
barry#endmeeting23:55
MootBotMeeting finished at 17:55.23:55
thumperthanks barry23:55
barrycheers23:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!