/srv/irclogs.ubuntu.com/2010/05/19/#launchpad-meeting.txt

=== Ursinha is now known as Ursinha-afk
=== mrevell__ is now known as mrevell
=== Ursinha-afk is now known as Ursinha
bac#startmeeting15:00
MootBotMeeting started at 09:00. The chair is bac.15:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:00
bachi, who is here today?15:00
gmbme15:00
sinzuime15:00
bacfor the launchpad reviewers meeting15:00
danilosme15:01
gary_posterme15:01
abentleyme15:01
gary_poster(mars will probably be absent)15:01
bacbigjools ping15:01
bacEdwinGrubbs: ping15:02
BjornTme15:02
EdwinGrubbsme15:02
bigjools\o15:02
leonardrme15:02
adeuringme15:02
noodles775me15:02
bacteam leads would you ping your absent folks15:03
deryckme15:03
gary_poster(foundations is as here as we're going to get)15:03
bacgary_poster: thanks15:03
henningeme15:03
gary_posternp15:03
bachi intellectronica, jelmer15:03
henningehi bac ;)15:04
jelmerhi Brad15:04
bacok, let's get started and hopefully some stragglers will appear15:04
bac[topic] agenda15:04
MootBotNew Topic:  agenda15:04
bac* Roll call15:04
bac * Agenda15:04
bac * Outstanding actions15:04
bac * Mentoring update15:04
bac * New topics15:04
bac   * ec2 failures update - bac15:04
bac   * Reviewer move to Friday? - bac15:04
bac * Peanut gallery15:04
bac[topic] outstanding actions15:05
MootBotNew Topic:  outstanding actions15:05
bacthere are only two outstanding actions...both assigned to me.15:05
bacbut i'm batting .50015:05
bac * bac to write community reviewer and contributor policy and announce it on the list. -- done15:05
baci got that out, as promised, before leaving for UDS.15:06
bacbut remain stalled on:15:06
bac* bac to define new doctest policy regarding what is "testable documentation".15:06
baci'll try to get to that next week15:06
bac[topic]   * ec2 failures update - bac15:06
MootBotNew Topic:    * ec2 failures update - bac15:06
bacactually, i was hoping to have mars give us an update but he's not here today15:07
gary_posterI can summarize maybe15:07
bacsinzui reported in our standup that work has been done but it is still very much a problem15:07
bacyes, gary_poster?15:07
gary_postermars has been investigating the problems on ec2 test.  As a workaround, he has disabled the Windmill tests on ec2.  This is obviously very suboptimal, but considered to be less sub-optimal than ec2 break one out of four times, which I gather is the rough stat.15:08
gary_posterHe will continue to try to figure out and address the underlying cauase so he can reinstate the windmill tests in ec215:08
* bac saw about 60% failure last time he tried15:09
gary_posternote that windmill tests still run in buildbot15:09
gary_posterso this is a testfix risk15:09
gary_posterhopefully I didn't get anything wrong; that's what I understand.  done.15:09
bacgary_poster: when tests hang, and the script kills itself after timing out, does it send a farewell email?  i think that would be a useful addition if not.15:10
gary_posterbac, that is on mars' backlog, and in fact will be one of the next things he does to address, yes.15:10
bacok, great15:11
bacgary_poster: when were the windmill tests disabled?15:11
gary_posterbac, IIRC, Monday, with issues; issues were resolved yesterday15:12
bacsinzui: did you see your tests disappear after that or before?15:12
sinzuiOne disappeared yesterday afternoon15:12
gary_postersinzui, bac, we'll need to bring this up to mars.  Would you like me to take that action ite,?15:13
gary_posteritem15:13
bacwe should all keep an eye on our ec2 tests and report to mars instances of them disappearing.15:13
gary_poster+115:13
bacgary_poster: that would be great.15:13
gary_posterok15:13
bac[action] gary to follow up with mars on ec2 problems.15:13
MootBotACTION received:  gary to follow up with mars on ec2 problems.15:13
sinzuigary_poster, I think my branch was within a few hours of the mailmanlayer shutoff. the issue may be fixed15:14
gary_postersinzui: ack wll pass along, thanks15:14
bac[topic] * Reviewer move to Friday? - bac15:14
MootBotNew Topic:  * Reviewer move to Friday? - bac15:14
bacour pool of reviewers has been pretty hard hit lately with personel changes15:14
bachttps://dev.launchpad.net/ReviewerSchedule15:14
bacright now, on fridays we only have adeuring working15:15
bacwould gmb or henninge entertain the idea of moving to friday?15:15
gmbbac, I believe adeuring is a Friday reviewer; I wonder if it's the best thing for hte bugs team to lose two devs on the same day... Not sure it matters though.15:16
adeuringnot that I would mind sharing reviews with gmb or henninge, but I think if we have somebody in a US timezone would be better15:16
bacadeuring: yes it would be better15:16
bacadeuring: but of the active reviewers in the americas we're spread pretty thin15:16
adeuringright15:17
gmbbac, I'm happy to do it if deryck's okay with the change.15:17
baci could move to friday but that leaves an americas hole on tuesday15:17
henningeI don't mind moving to Fridays15:17
deryckI don't know if I want gmb and adeuring sidelined fridays15:17
bacderyck: ok.  henninge do you mind moving again?15:17
henningebac: no problem at all15:18
henningebut, as was said, the problem is America15:18
* henninge wonders if he should move west ...15:18
bachenninge: let's not bring politics into the meeting15:18
henningelol15:18
henningeBut I was talking about the whole continent anyway ...15:19
bachenninge: why don't you try friday and if seems we have a problem i'll then switch15:19
henningeIt's in the way of any girl that wants to sail around the world...15:19
bac[action] henninge to move to friday review EU review slot15:19
MootBotACTION received:  henninge to move to friday review EU review slot15:19
intellectronicabac: on the same subject, note that there's a slot freein on monday EU. when i'm gone there will be no reviewer until abentley gets workin, and judging by the last few mondays there's a lot of activity around that time.15:19
bacintellectronica: i know.  i was hoping you'd change your mind before then.  :)15:20
henningeintellectronica: where are you going, what did I miss?15:20
bacintellectronica: you can always help out on mondays as a community reviewer!15:20
intellectronicawow, i managed to omit all those Gs. i'm not lolcat speaking, it was as accident15:20
intellectronica:)15:20
bacintellectronica: what is the date for you leaving?15:21
intellectronicahenninge: i'm leaving launchpad at the end of next week.15:21
henningeintellectronica: oh, too bad :(15:22
henninge;)15:22
bacin light of that, perhaps it would make more sense for henninge to move to eu-monday and i move to friday15:22
intellectronicahenninge: what can i do, all those monday review shifts finally got to me15:22
henninge:)15:22
bachenninge: let's talk about it off-line.15:23
henningebac: ok15:23
bac[topic] peanut gallery15:23
MootBotNew Topic:  peanut gallery15:23
bacany new topics?15:23
sinzuiorphaned commits15:23
sinzuiThis is the what we have so far: https://wiki.canonical.com/Launchpad/QATeam/OrphanedCommits/10.05-devel15:24
sinzuiUrsinha, noted that this class of landing was not tracked with bug tags last release15:25
bachard to have a bug tag with no bug.15:25
gary_posterFWIW, If we talk about this here, I'd be +1 on this simply leading to someone taking an action item to raise this on the mailing list15:25
sinzuiIn the examples I saw related to the registry team they were contributor branches that were not linked to bugs15:26
* mars is guilty of submitting build system cleanups without bugs.15:26
sinzuiDo we want contributor work to always have a link to a bug/spec15:26
baci think reviewers should be on the look out for any MP that isn't linked to a bug.  not saying it isn't sometimes appropriate but it should raise a flag.15:27
intellectronicasinzui: with contributor work it's even more important, because you want to help contributors plan and track the work before they start15:27
bacintellectronica: agreed.  so sinzui's suggestion is a good one, IMO.15:27
sinzuiOr in my case, remove part of the branch a week later because the feature is causing errors15:28
bacbut only 2 of the 10.05 orphans are from community15:28
sinzuiyes, there is another issue, but in the lp engineer case, flacoste assumes these are on the kanban board15:29
bacsinzui: well, that does help.  but if we're going to track qa with bug tags then it would make sense to *require* a bug or we lose all QA testing...unless we employ a separate tracking mechanism.15:30
BjornTbac: if all we want is to track qa, filing a bug automatically sounds like a good idea15:31
bacBjornT: at what point?15:31
* gary_poster idly thinks of a flag for branches that says "addresses" rather than "fixes"15:33
sinzuiThe tags are hard to visualise at the moment since the page is missing: http://people.canonical.com/~lpqateam/test-plan-report-10.05.html15:33
BjornTbac: the script that scans commits and add qa tags probably15:33
gary_posterwhere addresses means that it is an incremental step towards a bug15:33
gary_posterbut does not actually resolve a bug15:33
* gary_poster suspects this is a can of worms15:34
henningeBjornT: so it should create a bug if none is linked to the commit?15:34
BjornThenninge: if all we want is to track QA, yes, why not?15:35
marsgary_poster, that's why I'm not going to touch it :)15:35
gary_poster:-)15:35
bacsinzui: would you take an item to talk to QA and then make a proposal on the list, taking into account BjornT's suggestion?15:35
henningeBjornT: sounds like a good idea. Let's see if Ursinha likes it, too.15:35
sinzuiyes15:35
bacthanks curtis15:36
bac[action] sinzui to talk to QA about our QA tracking problem and create a proposal on the mailing list15:36
MootBotACTION received:  sinzui to talk to QA about our QA tracking problem and create a proposal on the mailing list15:36
bacany other topic?15:36
bac315:36
bac215:36
bac115:37
bacthanks for coming everyone.15:37
bac#endmeeting15:37
MootBotMeeting finished at 09:37.15:37
marsthanks bac15:37
henningeso, intellectronica, which team won you over and how? ;-)15:37
intellectronicahenninge: the summer won me over. in a couple of weeks i'll be out of employment and ready to rock'n'roll :D15:38
henningeintellectronica: oh, because you said "leaving launchpad", I thought it was within the company.15:39
henningeintellectronica: so you have nothing new lined up yet?15:40
intellectronicahenninge: nothing at all (other than some fun-related plans)15:40
henningeintellectronica: well, have fun, then! ;-D15:41
intellectronicahenninge: thanks!15:41
* Ursinha reads the backlog16:12
Ursinha<BjornT> bac: if all we want is to track qa, filing a bug automatically sounds like a good idea16:12
Ursinhawe dropped out that idea because some of the commits aren't really bugs16:12
Ursinhahenninge, ^16:13
henningeBjornT: ^ ;)16:13
henningeUrsinha: I think that is the  point.16:13
henningeUrsinha: To track even those commits that aren't really bugs.16:13
Ursinhahenninge, that's how the script would initially work, but I dropped the idea after chatting with francis16:14
Ursinhahenninge, and why would we need that?16:14
henningeUrsinha: we were talking about orphaned commits.16:14
Ursinhahenninge, I see now... but the point is that the orphaned commits aren't all the commits the don't mention bugs, but only those which should and don't16:16
Ursinhas/the don't/that dont/16:16
Ursinhahenninge, I guess that not a lot of those supposedly orphaned commits are really orphaned, maybe we could fix that by adding the bug tag to the commit message?16:19
Ursinhahenninge, making that a pqm requirement, maybe16:19
henningeUrsinha: I am not sure they have bugs. It did not sound like that.16:21
Ursinhahenninge, and they should?16:22
* henninge has little own experience, he always files bugs...16:22
Ursinhahenninge, that's why I love you :P16:22
* henninge blushes16:23
henningeUrsinha: well, jtv trained me that way ...16:23
Ursinhahenninge, I love him too :)16:23
henningeUrsinha: The question was "Should all commits have a bug so they are qa'ble".16:24
Ursinhahenninge, my personal opinion is no16:24
henningeI was not aware of the definition for orphaned commits that you just gave.16:24
henninge"should have bug bug don't"16:24
Ursinhahenninge, the idea of having a bug attached to a commit is to track the qa you have to do on it16:25
henningeUrsinha: you are the authority on QA here, so if that is your opinion, we are fine, I guess ... ;)16:25
henningeon the bug, you mean16:25
Ursinhaof course having a bug for real fixes is needed to track problems and future reference16:25
Ursinhabut now we really need to care about fixes that need qa, those need bugs16:25
henningeso the rule should be "If the fix will need qa, attach a bug. If it doesn't a bug is optional?"16:26
henningeUrsinha: don't all fixes need QA?16:27
Ursinhahenninge, I thought so, but it turns out some are just adjustments that not necessarily can be qaed16:28
henningeUrsinha: I'll put that on the agenda for next week's meeting.16:28
Ursinhahenninge, well, speaking roughly in practical qa terms, yes, but I'd like to have bugs to all problems we have, even the ones that result in commits we can't test16:29
Ursinhabut that's my wish :)16:29
Ursinhaor the ones that don't even need commits to lp tree to be fixed :)16:30
=== salgado is now known as salgado-lunch
=== salgado-lunch is now known as salgado
=== gary_poster is now known as gary-afk
=== gary-afk is now known as gary_posrer
=== gary_posrer is now known as gary_poster
=== salgado is now known as salgado-afk
bacthumper, rockstar: up for a reviewers meeting?22:33
rockstarbac, havin' our standup right now.22:33
thumperI might have to skip it this week22:33
bacrockstar: why do you schedule the standup during our meeting time?  :)22:33
bacthumper: ok.  not much said but talk about broken ec2  and rearranging of OCR schedules due to all the people moving around.22:34
bacnext week...22:34

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