[[DistributedDevelopment]] steering meeting to be held in {{{#ubuntu-meeting}}} on 2010-12-15 at 2100 UTC. = Agenda = * Action items * ajmitch to come up with questions/topics for next meeting (re: REVU) * poolie to send bzr rotation pitch to platform mailing list * barry & poolie to add work items to [[https://blueprints.launchpad.net/ubuntu/+spec/other-foundations-n-distributed-development-review-and-planning|UDD blueprint]] '''(done)''' * Work items for [[https://blueprints.launchpad.net/ubuntu/+spec/other-foundations-n-distributed-development-review-and-planning|natty blueprint]] * Bugs of interest: * http://pad.lv/674353 - graph packages built through UDD * http://pad.lv/556132 - don't drop SSH connection after sending 1GB; requested by kiko * http://pad.lv/375013 - support committing direct to stacked branches * bzr branches are too expensive to use for casual sponsoring, compared with downloading packages from my local mirror (slangasek) * [[https://launchpad.net/bugs/295274|(watch file support)]] - james_w and barry to sprint on that at uds-n * [[https://launchpad.net/bugs/653307|Import fails with missing referenced chk root keys]] * [[https://bugs.launchpad.net/bzr/+bug/603395|bzr commit in a heavyweight checkout does not propagate new tags]] * [[https://launchpad.net/bugs/653832|Import fails with "trying to import version ... again"]] * [[https://launchpad.net/bugs/499684|Interface to dpkg-buildpackage inconsistent and not well documented]] * http://pad.lv/608450 and others - ways to update debian/control and versions from a recipe * AOB = Summary = * ajmitch has some [[http://paste.ubuntu.com/544185/|initial thoughts]] about UDD and REVU * several fixes for bugs of interest are committed or in progress * next meeting 2010-01-12 {{{ ajmitch: For me one of the killer features of REVU that things like PPAs lack is the ability to hold multiple versions of upstream tarballs with identical names, but different contents and diff them. }}} = New Actions = = Log = {{{ #startmeeting Meeting started at 15:02. The chair is barry. Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] hi all hi folks and welcome to this week's udd stakeholder's meeting [16:03] https://wiki.ubuntu.com/DistributedDevelopment/20101215 [LINK] https://wiki.ubuntu.com/DistributedDevelopment/20101215 LINK received: https://wiki.ubuntu.com/DistributedDevelopment/20101215 who's here today? me * slangasek waves james_w: ? thumper: ? [16:05] hey! ajmitch: ? I'm kinda here thumper: how early in the morning is it for you? ;) barry: 10am oh that's not too bad let's start... [16:06] [TOPIC] action items New Topic: action items * ajmitch to come up with questions/topics for next meeting (re: REVU) i don't know if ajmitch is around, so let's leave that one for now * poolie to send bzr rotation pitch to platform mailing list sorry, not done [16:07] keep it cool * barry & poolie to add work items to [[https://blueprints.launchpad.net/ubuntu/+spec/other-foundations-n-distributed-development-review-and-planning|UDD blueprint]] * ajmitch is kind of here i did add some work items from our last meeting, but could use poolie's review of it ajmitch: hi. are you ready to talk about REVU, or should we push that back to next time? i think they're plausible there are a tonne of others, but i think they're good for ~april [16:09] I have some initial notes/comments about it poolie: cool. feel free to adjust, decompose, reassign, etc. as you will. the screenscrapers will keep up ajmitch: i'll put it on the agenda for later really rough list that I came up with to start a discussion at http://paste.ubuntu.com/544185/ ajmitch: cool. let's blow through the bugs and then talk about it [16:10] ok [TOPIC] bugs of interest New Topic: bugs of interest are there any updates on the bugs at the agenda url above? i know i have not had time to work on any of them :( some [16:11] a fix for direct commits to stacked branches is underway we did some network performance fixes i fixed a bzr builder bug, not sure if it was on the list exarkun should fix the conch breakage on huge pulls by january [16:12] and without browser atm oh, spiv i think fixed the tags thing good for you so, a decent bit of progress yep, really fantastic perhaps we should re-fill that list when we next meet (i assume in january) poolie: +1, and +1 [16:13] i've done a ton of branches in the last two weeks and have noticed two things that kind of hit me often. i'll describe them and perhaps you can tell me if bugs need to be filed [16:14] the first is that merge-upstream on maverick doesn't know about natty. i always have to fire up my natty vm, do the merge-upstream, push the branch to lp, and then go back to mav (my main dev box), pull the branch and proceed from there ouch [16:15] i think you should file a bug; james can close it if it's already fixed it sounds like at minimum a ui or doc gap poolie: will do, thanks *** jelmer____ (~jelmer@aurelia.vernstok.nl) has joined channel #ubuntu-meeting [16:16] the other thing i notice, and i'm not sure it's a bug, is that it's problematic to get the changelog entry right. dch -i doesn't cut it for a few reasons: barry: Wasn't there somebody looking at doing a SRU to cope with that? jelmer____: i dunno, but poolie or james_w might [16:17] bug 668764 Launchpad bug 668764 in bzr-builddeb (Ubuntu Maverick) "Add Natty to the list of known distros" [Medium,Fix committed] https://launchpad.net/bugs/668764 yeah ah, that's always bugged me too [16:18] apparently Pitti uploaded to maverick-proposed ah, cool thanks [16:19] so, dch: [16:20] * series always defaults to maverick instead of natty * 1build1 -> 1ubuntu1 I think there's a package that we can now use to answer these sorts of questions (which is the current target, what's available) * formatting of LP: #XYZ is finicky james_w: sorry, was that in response to my second issue? both really bzr-builddeb could use it so that I don't have to remember to add the new codename dch could use it so that it can know where to target by default (the maverick/natty issue) gotcha [16:22] i did file bug 690230 on the XbuildY issue [16:23] Launchpad bug 690230 in devscripts (Ubuntu) "dch -i should change XbuildY to NubuntuM" [Wishlist,Triaged] https://launchpad.net/bugs/690230 *** jelmer-n900 (~yaaic@a83-163-237-10.adsl.xs4all.nl) has quit: Quit: Yaaic - Yet another Android IRC client - http://www.yaaic.org james_w: do you think there are reasonable bugs i can file lurking in the second issue? barry, yes [16:24] I think there is some disagreement on the maverick/natty one, but hey I'm not sure how to make the fomatting easier, but no reason we can't try okay. i'll try to formulate a couple of bug reports. btw, should i be filing them on udd or bzr-builddeb? [16:25] that sort of thing can go against udd [16:26] james_w: cool, thanks devscripts is where dch lives, so that would be better, but maybe add a "udd" task? that's it for me, anybody else have feedback on bugs? [TOPIC] REVU [16:27] ajmitch: you have the floor New Topic: REVU 10:09 < ajmitch> really rough list that I came up with to start a discussion at http://paste.ubuntu.com/544185/ * ajmitch hasn't had much time to actually write up anything here but I was just wanting to hear peoples ideas of reviews of new packages [16:29] ajmitch: For me one of the killer features of REVU that things like PPAs lack is the ability to hold multiple versions of upstream tarballs with identical names, but different contents and diff them. [16:30] right, I'm not sure how that can be done by comparing different revisions of an upstream branch & how we'd use that properly [16:31] The problem we run into is poorly constructed tarballs that have to be redone. This is not rare. currently each upload to REVU is stored in a separate directory & diffs are generated between them Not rare, and is often done for legal reasons [16:32] ajmitch: is the directory kept once the package is accepted, or is it destroyed (perhaps also for legal reasons?)? jelmer____: currently kept until someone removes it through the UI ... are we stuck? [16:36] ajmitch: maybe we can talk more about REVU at the next meeting? i haven't used it enough to have any relevant comments barry: perhaps, if people want to ajmitch: okay, thank you though for that list. i'll add it to the summary [TOPIC] next meeting [16:37] New Topic: next meeting so, probably in january if we do the 5th, then the meeting after will be at the platform rally, which might be a good thing any objections to meeting next on 5-jan-2011? right, and the bzr team (including jelmer) will be there that'll be fantastic hm how many working days are there between now and the 5th? some and some people may hack over the holidays of course 7 i think? people do tend to disappear early, but yeah, holiday hacking is a great tradition :) [16:39] barry, the platform sprint is the week of the 5th sorry, of the 10th ie the week after the 5th d'oh! you're right. so, postpone next meeting until the 12th? wfm [16:40] me2 any objections? let's keep the same time of day yep which would be 15:00 US/Central? yes, but we'll be in US/Eastern, so it's 1600 oops, no [16:41] right 1500 US/Central i forgot where dallas was :) okay, then next meeting on the 12th, same time [TOPIC] AOB New Topic: AOB anybody have anything not on the agenda? [16:42] US/Somewhere-southish US/HopefullyWarm not from me 5 [16:43] 4 3 nope 2 1 see y'all in Dallas :-) #endmeeting }}}