/srv/irclogs.ubuntu.com/2006/09/04/#launchpad-meeting.txt

=== ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad-meeting
=== mpool [n=mbp@ozlabs.org] has joined #launchpad-meeting
mpoolddaa: hi, here?11:01
ddaaHello11:01
ddaahttps://launchpad.canonical.com/BazaarMeetingAgenda11:02
mpoolhm, so?11:04
ddaaMeeting in 54 minutes11:06
mpoolreally?11:06
ddaaWell, like every week...11:06
mpooloh, i used to have another one at 711:06
mpoolok, see you then11:06
=== lifeless [n=robertc@ppp245-86.static.internode.on.net] has joined #launchpad-meeting
ddaaYay12:00
ddaaMEETING STARTS12:00
ddaaThis is the launchpad-bazaar meeting, so there are more branches for use bazaar monkeys to hang about12:01
ddaa== Agenda ==12:01
ddaaNext meeting 2006-09-11, 10:00 UTC.12:01
ddaampool will be on leave.12:01
ddaaSay bzzzt if that does not fit.12:01
ddaa * roll call12:01
ddaa * production status12:01
ddaa * invalid branches12:01
ddaa * smart server12:01
ddaa * advertising12:01
ddaa * vcs-import knits12:01
ddaa * release finder12:01
ddaa * Python import12:01
mpoolddaa: both next week and the following week12:01
ddaa * bzr lp://12:01
ddaa * 1.0 targets12:01
ddaa * critical bugs12:01
ddaa * pending sysadmin tasks12:01
ddaa * proritizing important tasks12:01
ddaa * any other business12:01
ddaa== Roll call ==12:02
ddaaSpiv is on leave until September 10th.12:02
SteveAlength of meeting is?12:02
SteveA(in minutes)12:02
ddaa45 mins12:02
SteveAok12:02
jameshI'm here.12:02
SteveAi'm here12:02
lifelessmy fingers are here12:02
ddaagood enough12:02
ddaa== Prodution status ==12:02
ddaaEarly last week, abnormally long delay for mirroring sftp branches were reported. It was caused by a routing issue on escudero that caused time-outs for all vcs-imports branches.12:02
ddaaOnce escudero was restored, normal service resumed.12:02
ddaaA discussion is in progress (CC Launchpad mailing list) on how to rearchiture the branch puller to minimize latency in a future-proof way.12:02
ddaaI'm having trouble understanding lifeless' last email, but that's off-topic for this meeting.12:03
ddaa== Invalid branches ==12:04
ddaaLast week actions:12:04
ddaa * ddaa to bother jelmer about the bzr-svn bug12:04
ddaa * ddaa and lifeless to discuss bzrlib data validation. Not done.12:04
ddaaFollowing up on last week. I ack bzr should prevent bad data from getting in, but since shit happens, the supermirror should be able to recover without needing administrator intervention.12:04
ddaaI'm not too sure about how to do that. Does somebody has a plan and want to start the discussion?12:04
ddaaI do not think I got it across to jelmer last week.12:04
ddaalifeless and I did not have that discussion.12:04
ddaajamesh: lifeless: any clue about "supermirror recovery from invalid data"?12:05
lifelessddaa: like I said, I dont think there is a discussion to have12:05
SteveAis it a problem that is happening right now?12:05
lifelessI thought you had changed that as per the discussion we had *in last weeks meeting*12:05
jameshddaa: can the puller overwrite the invalid branch?12:06
ddaajamesh: I do not expect so, that's the issue12:06
ddaaACTION: ddaa to email to explain what he sees as a problem, since apparently it's not obvious12:06
SteveAif the problem is not occuring right now...12:06
ddaaSteveA: it's occuring right now12:06
ddaalet's move on12:07
jameshddaa: ideally we'd handle it in the same way as a branch format change: blow away the mirror and start again.  The question is whether we can differentiate between invalid data and bzrlib bugs12:07
SteveAhow much is it occuring?12:07
ddaaSteveA: all samba branches produced by bzr-svn12:07
jamesh(i.e. do we get a specific exception or random failures inside bzrlib?)12:07
ddaapotentially random failures, although this specific problem causes a BzrError.12:07
ddaa== Smart server ==12:08
ddaaLast week spiv said: lifeless & mpool & I will be meeting in person tomorrow to continue work on the smart server.  lifeless has figured out some good goals w.r.t. supermirror integration and HTTP integration that's the next step.12:08
ddaampool: status?12:08
mpoolwe did meet, 12:08
mpoollifeless: what was the last status you had from spiv before he left?12:09
lifelesshe was part way through splitting those branches12:09
lifelessI hope/imagine he has pushed his current set to chinstrap/sodium12:09
mpooli hope we can merge at least part of it for 0.11, and have andrew merge the corresponding bits to the supermirror when he gets back12:10
mpooli'm not sure if this is realistiic12:10
lifelesshes back with a week to spare for 0.1112:11
lifelesssome at least will land, I'm sure of it12:11
ddaaDo you think it's still on track for deployment before october 8th?12:12
mpoolddaa: not as much slack as i would like, but possible12:12
ddaa(I think that's the Launchpad 1.0 time)12:12
lifelessFull smart server deployment, no12:12
ddaalifeless: as opposed to what?12:12
lifelesswe're aiming for the RPC transport deployed into both the hosting and mirror environments12:12
ddaaI'm not clear on what is "full deployment" as opposed to "core support"12:12
lifelessthe smart server will be a launchpad-code-free addition on top of that as it goes into bzr12:13
ddaalifeless: so you mean that the smart server may be used for the publishing side, but the hosting side will be post 1.0?12:14
lifelessno12:14
mpoolddaa: i think we mean12:14
mpoolall the launchpad-specific code will be done by then (dog willing)12:14
mpoolbut it need more pulls from bzrlib to be really exciting12:14
ddaawhat is the risk level of those "extra pulls", is that just some tuning that needs to go through review and merge, or is there some tricky outstanding issues?12:15
mpoolddaa: where are you driving with these questions?12:16
=== lifeless up the wall
lifelesssorry, thats *what*12:16
mpoolheh12:16
ddaatrying to get a hang on the progress and Lauchpad 1.0 target delivery, since it seems I'm the one reporting on that12:16
ddaaand it's all very fuzzy to me12:16
ddaabut maybe it's a pointless excercice since it will be done when it's done and there is not anything we can do to make it happen faster12:17
mpoolok, so let's say it's likely we will have approximately alpha-level smart server support fielded by that date12:17
mpoolthe additional work in bzr will be to speed it up by doing higher-level operations12:18
SteveAi'm keen to be running a smart-server on the supermirror soon, even if it provides no benefit over regular sftp12:18
mpoolit is not risky in an architectural sense, i am confident it will go according to plan12:18
SteveAso that we will know about how it works practically12:18
mpoolSteveA: right, that's what we're aiming for first12:18
mpoolright12:18
mpooland also to shake out any lp integration issues12:18
lifelessSteveA: thats exactly what we've mapped out12:18
SteveAand we can then add extra commands/calls or whatever you call it12:18
mpooli think we should get spiv on that as soon as we can when he returngs12:18
lifelessmpool: hes already on it12:19
SteveAlater to incrementally improve it12:19
mpoolcool12:19
mpoolso can we call that closed?12:19
lifelessSteveA: yes exactly12:19
ddaaYup. I feel enlightened.12:19
SteveAthe 1.0 goal should be to have the smart server in operation12:19
lifelesshow about we talk about something that has not changed in the last week12:19
SteveAnot that it actually buys users anything immediately#12:19
ddaa== Advertising ==12:19
ddaaLast meeting actions:12:19
ddaa * spiv: blog about similarities between SVN and bzr checkouts, in relation to Launchpad.12:19
ddaa * ddaa: when rolled out, to blog about branch UI improvements.12:19
ddaa * unassigned: when rolled out, blog about --create-prefix not being needed anymore.12:19
ddaaspiv on vacation12:19
ddaaddaa and unassigned, waiting on rollout12:20
ddaamoving on12:20
mpoolddaa: i think we need in the medium term to do something more than blog to communicate about this12:20
ddaaThe blog thing appears to be working well enough for new.12:20
ddaafor *now*12:20
mpoolhow do you assess that?12:20
jameshbut how do people find these scattered howtos 6 months from now?12:21
ddaampool: I throw some chicken bones and read in them12:21
jameshIt'd be good to get them in a central location (or at least linked from a central location)12:21
lifelessany post should be put on bazaar-vcs.org/Welcome12:21
lifelessin the news area12:21
mpoolthey should be reachable from launchpad in an organized way12:21
ddaayeah, we need something more structured, maybe like the Malone/Rosetta docs, and link from that.12:21
mpoollifeless: somethin g kg like that12:21
jameshhelp.launchpad.net maybe?12:21
mpoolwe don't need to sort that out now12:21
mpoolindeeed it may be good to seek UI opinions from Uman or mpt or similar folks about where to put it12:22
ddaaaction for someone?12:22
mpoolyes12:22
mpoolSteveA: agree? who should do it?12:22
SteveAI'd like you or ddaa to put it on help.launchpad.net12:23
ddaamh... since mpool is working on critical things like the smart server, it might be a better idea to use my time for that12:23
mpoolddaa: that would be great12:24
ddaaACTION: ddaa to start compiling blog data on help.launchpad.net12:24
SteveAto start with, it's just a matter of making a page, linking it to the front page12:24
ddaaSteveA: happy to do no more than that, then :)12:24
mpoolddaa: actually, to *really* start with, just write a very small spec for how this is documented, and seek comments on hat12:24
SteveAI'd go the other way12:24
ddaaSteveA++12:25
SteveAhave a single place where we collect the documentation12:25
mpoolSteveA: implement first, comments later?12:25
SteveAthat is publicly accessible12:25
SteveAand then look for opportunities to better link it and put it on the bzr website or whatever12:25
SteveAbut we need to have the resource before we can use it12:25
ddaaI like the idea of producing raw material as blog posts and integrate that material in a central place.12:25
ddaabut, hey, we have more critical stuff to do now12:26
SteveAand jamesh made a good point about how people find the articles N months from now12:26
ddaaMoving on?12:26
SteveAanother option is having a "using bzr with launchpad" section on the bzr website12:26
SteveAdone12:26
ddaa== vcs-imports knits ==12:27
ddaaIt appears that the outstanding bzr patches have been merged to bzr.dev, what's needed now is a bzr update on rocketfuel.12:27
ddaalifeless: can you sync/cherrypick rocketfuel's bzr?12:27
ddaaThe last outstanding patch is launchpad/import-batch-progress. Should the BatchProgress code be submitted to bzr upstream, or should it stay in Launchpad?12:27
ddaahttps://devpad.canonical.com/~jamesh/pending-reviews/david/launchpad/importd-batch-progress/full-diff12:27
lifelesswe should just update to 0.1012:27
lifelesswhich has been released12:27
ddaalifeless: by all means12:27
lifelessthat may or may not include all the patches12:27
lifelessI think it has 1 of them12:27
lifelessits also much faster than the current bzr we're running12:27
ddaacan you cherrypick the missing bits as well?12:28
jameshmight even protect us from Jelmer's branches :)12:28
ddaaperformance is not our big issue ATM12:28
lifelessyou have already applied the fix to our branch right ?12:28
ddaalifeless: I cannot commit to rocketfuel's bzr12:29
lifelessok12:29
ddaaI rolled out a custom branch to importd when deploying the knits conversion code12:29
lifelessI suggest just updating to stock bzr 0.10 and keeping your extra fix whereever it is now12:29
lifelessthe second fix will be in 0.1112:29
lifelessand AFAIK we've done all the knit conversions right 12:29
lifeless?12:29
ddaalifeless: right, but it looks like there's a new upgrade to do soon.12:30
lifelessddaa: ???12:30
ddaaabout root id12:30
lifeless0.11 at the earliest12:30
ddaaokay, then it should be okay to temporarily regress on format converision support12:30
lifelessand as that will come in via bzr, I dont see that theres any relevance for these fixes to 'our bzrlib' - them being in the bzr that comes is is all thats needed12:31
ddaathe relevance is avoiding deploying custom bzr code to importd12:31
ddaabut I guess it's no longer necessary, as you point out12:31
ddaaWhat about the BatchProgress thing?12:31
lifelesswhat thing ?12:32
ddaait's the Progress class that gives heartbeat output for buildbot12:32
ddaaBah, let's move on.12:32
lifelessI dont know anything about that, other than you wrote it12:32
ddaaACTION: ddaa sort out what to do with BatchProgress with lifeless and mpool12:32
jamesh(we're 2/3 the way through the meeting timeslot, btw)12:33
ddaa== Release finder ==12:33
ddaaLast meeting action:12:33
ddaa * jamesh: report on Dyson full test run.12:33
ddaayeah, we're running late :(12:33
lifelessless discussion, more yes/no. DeferToList12:33
SteveAmeta: the thing to do here is either to agree to trip certain agenda points from the meeting, or agree with attendees for an extended meeting.12:34
jameshIt is definitely working better than before, but we got a new exception in the HTTP walker class when trying to read docbook.org indexes12:34
SteveAs/trip/strip/12:34
ddaaSteveA: I can just speed up some status report items12:35
jameshLooks like a simple mis-use of BeautifulSoup, so hopefully we'll have a better result next week12:35
ddaaokay, so still in the works, progress being made12:35
jamesh(I should be able to add tests for this failure pretty easily too)12:35
ddaa== Python import ==12:35
ddaahttps://launchpad.net/products/launchpad-bazaar/+bug/5636012:35
ddaaWas busy catching up, merging stuff and having design discussions via email. No progress on that. Need to decide on prioritization later this meeting.12:35
lifelessya, I'm nagging on the release finder regularly ;)12:35
ddaano need to discuss python import right now, later/post-meeting...12:35
lifelessdidn't we have prioritisation discussions for it last week ?12:36
SteveAjamesh: note that I updated our BeautifulSoup in mainline launchpad12:36
ddaa== bzr lp:// ==12:36
ddaaLast meeting action:12:36
ddaa * mpool: integrate comments to BranchIndirection12:36
SteveA...to the latest release12:36
ddaalifeless: not as such, as far as I recall12:36
jameshSteveA: yeah.  The way the code was using beautiful soup seemed to bypass the encoding detection, leading to problems with the non-ASCII page data12:36
ddaaI think that spec has not changed since last week. mpool, can you spend some time on that? (yes/no)12:37
SteveAjamesh: latest B.S. is stricter about unicode output12:37
SteveAddaa: mpool, mark and I talked a little about this today12:37
SteveAmpool said he'd update the spec12:38
ddaaokay, see you next week about BranchIndirection12:38
jameshSteveA: the p-r-f code is doing "soup = BeautifulSoup(); soup.feed(data)", which fails.  Doing "soup = BeautifulSoup(data)" works.12:38
ddaa== 1.0 targets ==12:38
ddaa[stripping some stuff that needs no discussion] 12:38
ddaabzr-roundtrip-svn: not for 1.0, but discussion is in progress on the bazaar-ng mailing list about how to make bzr-svn acceptable to importd.12:38
ddaampool: SteveA wanted to know what you were thinking of the general direction of this discussion.12:38
mpooli have not updated the BranchIndirection spec12:39
SteveAfeeding a soup is not usually adding things to a soup, but rather consuming the soup12:39
mpoolthe roundtripping discussion seemed ok to me...12:39
ddaa== Critical bugs ==12:40
ddaa[skipping that, simple status reporting, see the BazaarMeetingAgenda] 12:40
mpoolaction: mbp: read up/tick off svn roundtripping discussion12:40
lifelessFWIW sivs latest work is missing stuff done thursday and friday12:40
ddaampool: that would be nice12:40
ddaa== Sysadmin tasks ==12:41
ddaa[skipping that, see BazaarMeetingAgenda] 12:41
ddaa== Prioritizing important tasks ==12:41
ddaaThere are several important new tasks competing for our time. Spiv is out being even more smart and serving than usual, so it's between jamesh and me.12:41
ddaa * Removing Arch support. Low risk, relatively large (est. 16h ddaa). 1.0 target.12:41
ddaa * Python import, currently bug 56360. High risk (may have other hidden blockers), unknown size (est. at least 6h, at most ???).12:41
ddaa * Bug 31308 (native productseries branch) Low risk, medium sized (est. 8h).12:41
=== SteveA wonders about having a "before you go on leave" wiki article... (1. mail people about outstanding work. 2. push all your branches...)
ddaaTo that, I would like to add: bug 34540 (cannot delete a branch) which I think is the largest remaining barrier to adoption of the branch registry. Just allowing to disable branches, without implementing garbage collection should be relatively simple.12:41
ddaa * Bug 34540 (cannot delete a branch). Low risk, medium sized (est. 8h).12:41
ddaaSince all those tasks look very important and urgent to me, I suggest:12:41
ddaa * ddaa: removing arch support and python import.12:41
ddaa * jamesh: productseries branch and deleting a branch.12:41
ddaaSteveA: what do you think?12:41
ddaaOkay, that's one item I want a decision on, but can be discussed post meeting (lifeless and mpool not really required for that)12:42
jameshddaa: I'm also working on automatic BugBranch link creation now, btw12:42
SteveAI'd like to see the python import set off, cos I want to see whether it will break and how.12:42
ddaaSteveA: IMO arch support removal takes priority as it's a 1.0 goal12:43
SteveAremoving arch support doesn't cost us anything to delay a while12:43
jamesh"productseries branch" refers to switching to import_branch and user_branch, right?12:43
ddaajamesh: yes12:43
SteveAddaa: it doesn't buy us anything this week, but having a python import does12:43
ddaaSteveA: okay12:43
lifelessddaa: removing arch support has been turned down by steve in the last 4-5 meetings I can recall12:43
lifelessddaa: I'd really like it to stop being an agenda item, its wasting cycles12:44
SteveAddaa proposed it as a task for him and tim p. to do together, which I rejected12:44
SteveAI think ddaa should do it, but I think it is better to do python first12:44
SteveAbecause it is estimated as less time12:44
SteveAand it has more overall benefit, imo12:44
mpoolafter that i'd like to suggest working on a firefox import12:45
mpoolif there is not already one12:45
mpoolthey're looking at moving from cvs12:45
mpoolSteveA: maybe you should add "before you go on leave" to the policies wiki?12:45
lifelessok, piss-break before the review meeting12:45
jameshmozilla/firefox makes heavy use of CVSROOT/modules aliases12:45
ddaawhich is not really supported by importd12:45
lifelessmozilla will melt your brain12:45
ddaaanyway, that's offtopic for that discussion.12:46
ddaaSteveA: jamesh: I think native-branch-for-series and deleting-branch are more important than bug-branch stuff12:46
ddaaare they are important blockers in the existing system12:46
ddaaI'd like very much to see progress on those, but I do not think I will have the time soon.12:47
SteveAddaa: let's talk about your priorities etc. later today12:47
ddaaFine.12:47
jameshI've only done some speccing for the bugbranch stuff, so I can easily move over to the productseries branch stuff12:47
ddaa== Any other business? ==12:47
ddaaOne minute to say "hey!".12:48
mpoolhey!12:48
mpooltwo things12:48
jameshI wouldn't mind some comments on https://launchpad.canonical.com/AutomaticBugBranchLinks after I flesh it out a bit more12:48
mpoolfirstly, everyone in this meeting should read the 32/Bazaar spec12:48
mpoolhttps://wiki.canonical.com/32/Bazaar12:48
mpoolddaa, thanks for your commens12:49
mpoolif you have not, please do so before next week12:49
ddaajamesh: post to the LP mailing list CC key people when you've done the fleshing out12:49
SteveAddaa: jamesh, mpool and lifeless and I had a meeting earlier today about getting jamesh to do some work on the bug-branch stuff and lp://// stuff.12:49
mpoolsecondly, following on from what you just mentioned12:49
mpoolthere are a few bzr-lp features we need to focus on 12:49
mpool- launchpad-url12:49
mpoolaka branch indirection12:50
mpool- redirecting from a branch page to branch content12:50
mpool- native branches for products, as you just mentioned12:50
mpooland bug-branch connections12:50
mpoolmany of these require both bzr and lp changes12:50
mpooli think jamesh owns bug-branch connections now,12:50
mpoolhow about the others?  any comments on who's looking after them, or relative priority?12:51
mpoolor whether they're for lp 1.0?12:51
ddaamy pet peeve ATM is branch-delete12:51
ddaaI really think it's an adoption blocker12:51
SteveAddaa: i want to learn why you think that, but let's talk later today about it12:52
jameshbranch-delete may be in less demand when branch move/rename is available12:52
mpoolnot having any main branch for bzr is a peeve for me12:52
jameshit is often a case of "I put the branch in the wrong place and now want it deleted"12:52
ddaajamesh: certainly12:52
mpoolddaa, it sounded like you worked out with mark the changes that would be necessary to fix that, is that true?12:52
ddaampool: there was an email discussion between sabdfl and jamesh while I was on vacation12:53
jameshmpool: ddaa proposed I look at this bug (see "productseries branch" earlier)12:53
ddaasabdfl essentially approved the direction we are taking, without reservation, after a few explanations from jamesh12:53
mpoolok, so it's all good? not blocked?12:53
ddaablocked on getting somebody to actually do it :)12:54
ddaaIf jamesh can do it this week, I'm cool with that. Delete can wait another week or two.12:54
ddaasince it's not a technical prereq for anything else12:55
mpoolok, well, it's not for me to say who will do it12:55
mpoolthat's between you, stevea, jamesh & others12:55
mpooli just want to make sure it's flowing along12:55
mpoolbranch indirection is blocked on me fixing the spec12:56
mpoolfor example.12:56
ddaaOkay, I'll put it on the top of my "jamesh please" list :)12:56
jameshokay12:56
mpoolok, how about redirecting from pages to brnahces?12:56
SteveAmeta: should have agreed an extension to the meeting.12:56
mpoolthere are bugs open, i don't know their numbers.12:56
=== ddaa flogs himself
jameshsetting the productseries branch is a prereq for a bunch of other stuff, so I'll try and get it sorted this week12:57
jamesh(e.g. the branch indirection spec)12:57
mpooljamesh: that's true; doing it soon would be great12:57
mpoolgood point12:57
ddaampool: I sugges that you revive the discussion that on the mailing list, so we can take the time to dig up the bugs etc.12:57
mpoolok12:57
mpoolok, that's all then12:57
ddaaMEETING CLOSED12:58
SteveAthanks david12:58
ddaaThank you all for your attention.12:58
ddaaSorry for being late.12:58
SteveAafter the review meeting, i'll be going for some lunch12:58
=== ddaa will going for lunch now
SteveAand when I get back, I'd like to talk with you about these tasks12:58
ddaaunless somebody wants to talk to me about something right now12:58
=== ddaa -> lunch
ddaaSteveA: ping02:48
SteveAhi ddaa03:29
SteveAddaa: ping03:35
ddaawas workraving03:36
ddaaSteveA: you wanted to talk about the tasks for the next weeks03:37
ddaafirst, I'd like to talk meta-meeting03:38
SteveAok03:38
SteveAshall we have a voice call?03:38
ddaaplease no03:39
SteveAporquoi?03:39
SteveA^u03:39
ddaaI have some distraction at home, between the kittens and the gf who is having a one week sick leave03:39
SteveAthat's not really a good reason03:40
ddaawell okay03:40
ddaalet's have voice03:40
SteveAskype okay?03:40
ddaashould work03:41
ddaaor ekiga if you prefer, works okay here03:41
SteveAi've had not much success with ekiga03:42
SteveAprobably need to change my router03:42
SteveAso, let's do skype today03:42
SteveAi'm running skyep03:43
ddaasetting up03:43
SteveAbut i don't seem to have you listed at all in my addressbook03:43
ddaadavid.allouche03:44
ddaaI cannot seem to get online for some reason...03:45
ddaaIt seems I cannot get online.03:45
SteveAwell03:47
SteveAi just tried adding you to my skype contacts 03:47
SteveAand I get an error03:47
SteveA"david.allouche was added to your Contacts, even though the Skype Name was not found03:47
SteveAThe Skye Name does not exist or this person has not been online for a long time"03:47
ddaaI got online like a couple of moths ago03:48
ddaabut it does not work now03:48
ddaalet's try ekiga03:48
SteveAafter a few months, they remove your account03:49
SteveAi'm running ekiga now03:50
ddaaone minute please03:50
SteveAhttps://wiki.canonical.com/VOIP/Extensions03:50
ddaabingo, she got angry at me because I wanted to be alone for the call03:52
ddaaoops04:22
SteveAwhat happen?04:22
SteveAsomeone set up us the bomb?04:22
ddaasound got scrambled, I reset the connection04:22
SteveAok, i just hung up04:23

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