=== ubuntulog [i=ubuntulo@trider-g7.fabbione.net] has joined #launchpad-meeting === SteveA [n=steve@213.133.64.221] has joined #launchpad-meeting === lifeless [n=robertc@ppp245-86.static.internode.on.net] has joined #launchpad-meeting === mpool [n=mbp@ozlabs.tip.net.au] has joined #launchpad-meeting === jamesh [n=james@203-59-178-78.dyn.iinet.net.au] has joined #launchpad-meeting === sivang [i=sivan@muse.19inch.net] has joined #launchpad-meeting === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad-meeting [11:57] ddaa: last week's minutes are here: https://launchpad.canonical.com/BazaarMeeting20060821 === spiv [n=andrew@218-214-66-203.people.net.au] has joined #launchpad-meeting [11:59] jamesh: thank you, I've read them already [12:00] MEETING STARTS [12:00] This is the Greenhouse meeting, on techniques of growing Bazaar branches in a Launchpad, if that means anything. [12:00] I am just coming back from vacation, so I'll let you guys do most of the talking today. [12:00] jamesh: thank you for last week's meeting minutes, it's very good. [12:00] == Agenda == [12:00] * Roll call [12:01] * Production status [12:01] * Smart server [12:01] * Advertising [12:01] * vcs-imports knits [12:01] * Release finder [12:01] * Python import [12:01] * bzr lp:// [12:01] * 1.0 targets [12:01] * Critical bugs [12:01] * Sysadmin tasks [12:01] * Any other business? [12:02] == Roll call == [12:02] mpool apologized. [12:02] I'm here [12:02] hi [12:02] I'm here [12:02] SteveA: hey? [12:03] SteveA late :P [12:03] == Production status == [12:03] Anything to report? [12:03] jamesh: how is the future of oops-from-scripts looking? [12:04] haven't looked at it at all since last meeting [12:04] lifeless: do you know if jelmer fixed the bug in bzr-svn? [12:04] no [12:04] We would probably have to purge the filesystem data for his branch when he has fixed them. [12:05] ACTION: ddaa to bother jelmer about the bzr-svn bug [12:05] he should bump his namespace [12:05] the revisions are corrupt, no telling how far its spread [12:05] we still need to make sure data like that doesn't get past the puller [12:06] lifeless: know how we can achieve that? Past discussion we had about that I remember as inconclusive. [12:06] note it in the bug thats already open [12:07] ACTION: ddaa to resume discussion about filtering bad branches in the puller [12:07] == Smart server == [12:07] mpool said: We've continued work, most recently pairing with Andrew on [12:07] letting it be run over ssh. Andrew can report more. [12:07] ddaa: no, thats not what I said [12:07] ddaa: dude, I said 'jelmer should bump his revision namespace' [12:07] lifeless: okay, will say that in the bzr-svn bug [12:08] but there is the separate issue that jamesh mentioned [12:08] I'm happy not to fix it for now though. [12:08] Right, so the code to run the protocol-so-far over SSH is basically there. [12:08] its not the pullers problem, I really think its purely a bzrlib bug if it happens, file a bug and we'll fix it [12:08] Lots of the infrastructure for that has been submitted for merging to bzr.dev, and is ready to go into 0.11 [12:09] talk with me after the meeting, so we dont block now. But I dont think we should design the bzrlib fetch code twice. It does not make sense. [12:09] lifeless: okay. But the puller should be able to recover w/o manual intervention, and I do not think I can ATM. [12:09] spiv: sounds great [12:09] == Advertising == [12:09] spiv: should I make you the current owner of this task about blogging on similarities between SVN and bzr checkouts (in relation to Launchpad of course)? [12:10] 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:10] hi [12:10] i'm on a public holiday [12:10] after the next rollout, we'll be able to advertise that --create-prefix isn't necessary anymore [12:10] ddaa: yes, in fact I've actually got a draft already [12:10] Okay, sorry for not taking notes, I have not yet handled the email backlog. [12:10] SteveA: ^ [12:11] When the fixes to the greenhouse UI are rolled out, I'll probably post something about that too. People have been asking for that for a long time. [12:11] greenhouse ? [12:11] launchpad-bazaar = greenhouse [12:11] did I miss something ? [12:12] There was some discussion in the past about that, sabdfl appeared keen to have a cute name, and I like a shorter name. [12:12] So I sent an email to the launchpad mailing list to "codify the status quo" [12:12] oh :(. Its about as good as dyson was IMO. [12:13] lifeless: I'll adopt anything you can agree on with sabdfl [12:13] how about launchpad-bazaar? Clear, precise, to the point. [12:14] ddaa: most areas of Launchpad are being debranded in the UI (e.g. blueprint => features), so at most it would be an internal codename [12:14] it will be called "code" in the launchpad UI [12:14] I'm not the one pushing for using cute code names. I'm merely trying to make the boss happy, and taking the opportunity to save a few keystrokes. [12:15] I see where you're coming from. Honestly, I think it creates more keystrokes all round. [12:15] because people have to ask about it [12:15] and it isn't a "sticky in your mind" name like "rosetta" [12:16] SteveA: I'm happy to abandon "greenhouse", but please post a followup to my mail on the launchpad mailing list. [12:16] I have no desire to risk an argument with sabdfl about that issue. [12:16] I dont think it is even worth discussing [12:17] should we move on? [12:17] Okay, then the issue is closed. [12:17] we can just agree to use the obvious "launchpad-bazaar" [12:17] == vcs-imports knits == [12:17] Apparently all deployed. [12:17] Still a couple of outstanding bzr branches. Have been reviewed, will act on reviews during the week and coordinate with lifeless about getting the patches in rocketfuel. [12:17] ACTION: ddaa to advance merging of outstanding bzr fixes into rocketfuel. [12:17] and we'll understand mark or others if they use "greenhose" [12:17] SteveA: ++ [12:17] but we can choose to use "launchpad bazaar" [12:18] lifeless: anything interesting to report about the progress of those patch in the bazaarsphere? [12:18] ddaa: they are both in the stack of patches spiv is managing [12:19] spiv: does that mean that I do not have to do any more on those patches? [12:20] silence is consent [12:20] == Release finder == [12:20] jamesh: did stub do a test run on staging this week, as reported on the last meeting? [12:20] yes [12:20] I don't know anything about ddaa's upgrade-no-workingtree branch [12:20] spiv: okay, then I'll apply some traction there. [12:20] But the list_dir one I'm on top of, yes. [12:20] ran into another bug (bug 57220), which I'm working on a fix for [12:21] hopefully we'll complete a full run with that problem fixed. [12:21] spiv: I referred it to you in reply to a mail from John on the list. [12:21] lifeless: Thanks, I'll take a look [12:22] jamesh: good, so next week I'll ask about the outcome of the full staging run [12:22] yep [12:22] == Python import == [12:22] https://launchpad.net/products/launchpad-bazaar/+bug/56360 [12:22] Was on leave, so made no progress on that. [12:22] Plan to look at this problem, but after acting on outstanding patches and giving spec feedback. Probably not come around to it this week. [12:23] == bzr lp:// == [12:23] Last week's action were: [12:23] spiv: read the spec [12:23] mpool: read/integrate comments [12:23] Progress? [12:23] I'm pretty sure I gave feedback on the spec. [12:24] Yeah, I did. [12:24] you appear to have, yes. [12:24] Okay, so the ball is in mpool's camp. [12:24] Yep. [12:25] ACTION: mpool to read/integrate comments on BranchIndirection [12:25] == 1.0 targets == [12:25] smart server: is that still on track for the end-of-month deadline? [12:25] importd bzr transition: the essential functionality was delivered. I'd like to put that on hold until we have the new hire, and have him do the Arch support wipeout. [12:25] SteveA: is that okay? Hom to update the spec? [12:25] bzr-roundtrip-svn: in my understanding, we will achieve that by replacing cscvs by bzr-svn when/if we feel comfortable enough with that. [12:26] I thought roundtrip was cancelled for now [12:26] roundtrip-svn: that means the status of this spec should be changed, since no further action is expected before 1.0 [12:26] I got heat from sabdfl by closing the spec as "not for us", because it means something specific to ubuntu folks. [12:27] So I restored it to the previous status. [12:27] apparently it means 'never' [12:28] as roundtrip is clearly a nice thing to do if we ever get around to it, I'd say 'low' [12:28] quoting sabdfl: [12:28] "Not for us" has a specific meaning, in the text of any spec with that status you will see it. Basically it means "this spec is regarded as pointless and not interesting to the project managers, we will not land any code for this even if you contribute it". [12:28] If you want to say "we are not going to work on this now", then Lowpriority would be more appropriate. [12:28] "not for us" was coined as a nicer way of saying bugger off [12:28] Should we also remove the 1.0 target as well? [12:29] if it isn't a 1.0 target anymore, then I'd guess so [12:29] I'd guess so, but you know what you say about burned cats. [12:29] spiv: is smart-server on track for the end-of-month deadline? [12:30] SteveA: do you agree on postponing Arch cleanups to give to the new recruit? [12:31] SteveA is not here [12:31] the smart server is not complete. [12:31] Ah, right. On holiday... [12:31] ddaa: I have no idea of how extensive the arch cleanups are [12:31] we're aiming to land the core transport and get launchpad support for it in side the 0.11 dev cycle [12:32] as in, how long it would take one knowledgeable, capable person to do so [12:32] What lifeless said :) [12:32] lifeless: does that leave enough room to get it up on launchpad by the end of the month? [12:33] no [12:33] 'not finished' [12:33] So I think we need to say this spec will be late. Okay. [12:33] end of the month is 3 days away [12:34] jamesh: I mean the end of next month :) [12:34] ddaa: then you might have said [12:34] yes, we will have the core support rolled out by end of next month === spiv agrees [12:35] IF things go smoothly, that might include the performance improvements too [12:35] SteveA: I think a couple of days for me. It's large and sweeping but simple now. I'm suggesting to postpone because I think that's a good exercice for the new recruit to see a lot of the importd code. [12:35] this is my compatriot ? [12:36] lifeless: I think it would be good to get something up on launchpad once there is working code, so we can shake down potential operational issues in parallel with performance improvements. [12:36] well, s/we/spiv/ [12:37] lifeless: yes [12:37] ddaa: we have a plan for that that is low risk, and staged [12:37] ddaa: can we move on? [12:37] I'm still not clear on whether the feature is on target, but let's move on. [12:38] == Critical bugs == [12:38] https://launchpad.net/bugs/31308 Cannot set branch associated to a product series. [12:38] https://launchpad.net/bugs/37897 renaming project, product or series breaks vcs imports. [12:38] https://launchpad.net/bugs/51130 cannot use +admin on a branch I own [12:38] I plan to act on reviews for 37897 and 51130 this week. [12:38] Plan to start work on 31308 after that and spec feedback, so late this week or early next week along with bug 56360. [12:38] IOW, I do not plan to do any new stuff this week. [12:38] == Sysadmin tasks == [12:38] == Any other business? == [12:39] none from me [12:40] mbp said something about [12:40] new item: Strategic planning document: mbp will need feedback on this [12:40] from people in the launchpad-bazaar team; watch for mail in next couple [12:40] of days. If you have ideas let me know. [12:41] Not sure exactly what that means, but I think it's related to the post-1.0 planning discussion. [12:41] its not [12:41] watch for a mail [12:42] Okay. Then if there's nothing more to discuss [12:42] the bazhouse meeting can be closed [12:42] or the greenzaar [12:42] MEETING CLOSED [12:43] Thank you everybody for attending. [12:43] oh right [12:44] ACTION: spiv and ddaa to review PrivateBranches again [12:44] I think I saw something from spiv recently, will try to do my part this week too. [12:44] ddaa: so, I don't think doing the arch removal stuff is good material for the new bzr=launchpad recruit [12:45] i think implementing private branches would be better, for example [12:46] Okay, if that's what you think. [12:47] We'll talk next week about how to prioritize that work against the Python import and the native-productseries-branch thing. [12:47] ok [12:47] to save me asking tomorrow... [12:47] what do you plan to do during this week? [12:47] Email catchup [12:48] Reply to reviews, try to get outstanding branches merged. [12:48] I have a lot of those. [12:49] So I expect that to keep me busy until friday at least. I may have some time at the end of the week to start doing some new stuff. [12:49] what are the branches? [12:49] david/bzr/upgrade-no-workingtree [12:49] david/launchpad/importd-bzr-native [12:49] david/launchpad/branch-edit [12:49] david/launchpad/importd-publish-source [12:50] The latter is going to need some doing to deploy too. [12:53] Also, do PrivateBranches spec review and maybe some BranchIndirection. [12:53] SteveA: sounds reasonable? [12:54] what is branch-edit about? [12:55] Letting people change the name, owner and product of branches. [12:57] ok [12:57] I've got a lot on this week, but I'd like to keep up with how these things are going [12:57] would you ping me occassionally on irc for a brief chat about how things are going? [12:58] If you wish, I can report daily. [12:58] But I expect that to be relatively uneventful. [12:58] that's fine [12:58] thanks! [12:59] have a nice holiday [12:59] and get away from the computer [01:05] thanks, and I will