/srv/irclogs.ubuntu.com/2010/12/01/#ubuntu-meeting.txt

=== jjohansen is now known as jj-afk
=== rsalveti` is now known as rsalveti
=== deegee_ is now known as deegee
=== Agent001 is now known as Agent007
=== emma is now known as em
=== apachelogger is now known as releaselogger
=== yofel_ is now known as yofel
=== niemeyer is now known as niemeyer_lunch
=== releaselogger is now known as apachelogger
=== niemeyer_lunch is now known as niemeyer
=== niemeyer is now known as niemeyer_testing
=== niemeyer_testing is now known as niemeyer
=== bilalakhtar is now known as cdbs
dokohi16:01
evhi16:03
mvohello16:03
robbiewo/16:03
jhunt_hi16:04
jhunt_you _can_ all hear me now right? :)16:04
dokoohh, had we a mumble session?16:06
robbiew#startmeeting16:06
MootBotMeeting started at 10:06. The chair is robbiew.16:06
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:06
evjhunt_: yes ;)16:06
robbiewdoko: uh...every week ;)16:06
robbiew[TOPIC] Lightning Round16:07
MootBotNew Topic:  Lightning Round16:07
robbiewpsurbhi is on holiday16:07
robbiewokay....who's up first....16:07
robbiewdoko?16:07
robbiew:)16:07
dokospent most time on internal work, besides this: dso linker fixes, python 2.7.1 and 3.1.3 releases, openjdk-6 after-security-math, and some linaro work with hrw16:08
doko--16:08
robbiewthnx16:09
robbiewand thanks for all the "internal work" ;)16:09
robbiewcjwatson?16:09
cjwatsondone: fixed some issues with new grub2 snapshots; moved non-first kernels into a submenu; patch pilot day on Tuesday, hoovered up a reasonable amount of sponsorship reqs and old bugs; helping out with alpha-116:10
cjwatsontodo: assemble initial blacklist for grub2-boot-framebuffer and package it somewhere (carried over)16:10
cjwatsoner, patch-pilot day on *Monday*16:11
cjwatson--16:11
robbiewthnx16:12
robbiewev?16:12
evTrying to sort out this damned installer testing nonsense with IS, working on a ubiquity implementation of the automatic partitioning home preservation stuff (already done for d-i), had a meeting with ivanka and some agency people on one of her projects, working out a battle plan for testing more of the installer.16:12
evdone16:12
cjwatsonoh!  I forgot about going down to London on Friday to talk with ev etc. about wubi16:12
evoh yeah16:13
evI did that too16:13
ev;)16:13
dokoinstaller nonsense?16:13
evtesting the installer on a giant pile of netbooks hooked up to honeysuckle.millbank, driven by hudson16:13
evit works in principle16:13
evjust needs some IS love16:13
dokoahh16:13
robbiewthnx ev!16:14
robbiewmvo?16:14
mvoapt: merges; very first patch pilot; general merges; Msttcorefonts: uploaded to natty and maverick and improve failure condition for the EULA stuff; software-center: work on startup and long list display performance, setup daily builds; update-manager: bugfixes, add chroot mode that will skip kernel selecton, started on screen integration (server mode only); vmbuilder: tiny amount of work16:15
mvostartup-speed is doing nicely16:15
mvolist speed in a experimental branch is also shaping well16:15
mvofingers crossed for a much speedier version soonish16:15
mvo(done)16:15
robbiewmvo: cool...you ordered your test machine, right?16:16
mvoyeah, its here and the first set of tests is done16:16
robbiewsweet16:16
mvohttp://people.canonical.com/~mvo/software-center/mini10-startup/startup-times.png16:16
MootBotLINK received:  http://people.canonical.com/~mvo/software-center/mini10-startup/startup-times.png16:16
mvoits not very impressive currently though16:17
mvostill a nice dent already16:17
evmvo: what are you using to measure this?16:17
robbiewooooh...nice16:17
mvo*cough*16:17
evand do you have it documented anywhere16:17
* robbiew suspects mvo has a stopwatch16:17
mvowhile gtk.events_pending(): if window_main.flags() gtk.VISIBLE: break16:17
robbiewlol16:17
mvoa precise one!16:17
Keybukev has a whole cupboard full of mini 10s :p16:18
Keybukwhich I'm sure he's only using as bittorrent seeders16:18
mvolol16:18
evpretty much16:18
robbiewthnx mvo16:19
robbiewbarry?16:19
mvoI'm open for other ideas how to measure this, it seems to be working ok16:19
barrypython: soabi patch committed, issue closed; fixed problem w/--enable-shared.  py27 ftbfs in natty: 662611 (virtualenv); 674175 (vte); 672209 (mutiprocessing); working on 683182 (graphviz).  submitted bug+patch for cheetah and svn to debian & bug 605365 discussion.  tomorrow: patch pilot.  done.16:19
ubottuBug 605365 on http://launchpad.net/bugs/605365 is private16:19
barrythanks for nothing ubottu16:19
robbiewheh...thnx barry........heh...thnx barry16:20
robbiewfigured I'd keep the echo16:20
robbiew:P16:20
barry:-D16:20
robbiewjhunt_: ?16:20
jhunt_Finished upstart bash-completion script and submitted for review on 25 Nov (http://article.gmane.org/gmane.comp.shells.bash.completion.devel/2695).  No response from mailing list. Anyone have any thoughts on how long it should take them to respond? Is there are more direct route? After chatting to keybuk, spend day working out my weird mountall system hang. There are some potential tweaks we could make to upstart/mountall to avoid this problem occuring.16:20
jhunt_Process question: what should I do re the "affect dpkg" on lp:#674146 (Ubuntu natty-alpha-1 milestone)? It isn't actually a dpkg issue and I think this bug may be appearing on skaets list. None of the status options look appropriate so I guess I want to just remove the dpkg entry entirely?16:20
robbiewbug 67414616:21
ubottuLaunchpad bug 674146 in dpkg (Ubuntu Natty) "dpkg segfaults during debootstrap on natty armel" [High,Confirmed] https://launchpad.net/bugs/67414616:21
jhunt_I tested a dpkg build with dokos patched gcc and it worked fine on kakadu.16:21
jhunt_it's not a dpkg issue though.16:22
* doko already forgot about the toolchain updates :-/16:22
barryjhunt_: mark it invalid?16:22
robbiewyeah16:22
robbiewmark it invalid for the dpkg task16:22
dokojhunt_: is dpkg rebuilt with default optimizations?16:23
jhunt_I guess. Should I update https://wiki.ubuntu.com/Bugs/Status though as it isn't clear that that status can be used for this scenario?16:23
cjwatsonbash-completion> find one of the maintainers on IRC and chase them up that way?16:23
cjwatsonprobably best to just rebuild dpkg and close the bug when that's done16:23
jhunt_k. I was following their documented process, but... :)16:24
robbiewjhunt_: if it's not a dpkg issue, then it falls under "This should also be used if the reported problem is not a bug at all, but for example user error "16:24
cjwatsondpkg does need to change, in a very technical sense of "be uploaded with no source changes"16:24
robbiewah16:24
cjwatsonactually, there would be a source change to undo jhunt's workaround16:24
cjwatsonit's more a "task" than a bug, but we don't have separate trackers for those really16:25
barryso, then yeah.  upload the change and fix committted16:25
robbiewjhunt_: yeah...what barry said ;)16:25
jhunt_so forward a new patch to undo my last one to cjwatson ?16:25
cjwatsonaye16:26
jhunt_thx16:26
cjwatsonafter alpha 1, though16:26
jhunt_k16:26
jhunt_EOT16:26
robbiewjhunt_: thnx16:26
robbiewKeybuk: ?16:26
KeybukI'm afraid I don't think I've accomplished anything to report this week :-(16:26
dokothere was a techtalk ... rumors ...16:27
robbiewheh..indeed16:27
Keybukthat was last week16:27
robbiewhttp://blip.tv/file/444439616:27
MootBotLINK received:  http://blip.tv/file/444439616:27
robbiew\o/16:27
robbiew[TOPIC] Natty Stuff16:28
MootBotNew Topic:  Natty Stuff16:28
robbiewAlpha 1 tomorrow16:28
robbiew...hopefully :P16:28
* robbiew hasn't been closely tracking feature work...but will start now16:29
dokoI'm planning to start a test rebuild tomorrow16:29
dokostill while the archive is frozen16:29
robbiewdoko: ok16:30
robbiewbarry: any plans to have work items for http://blueprints.launchpad.net/ubuntu/+spec/other-foundations-n-distributed-development-review-and-planning ?16:30
barryrobbiew: i really should get together w/james_w and figure that out ;)16:30
barryi'll try to do that today16:31
robbiewthnx16:31
dokopython2.7 as the default16:31
barrywe still have a little time to decide that16:32
robbiewdoko: any work items for http://blueprints.launchpad.net/ubuntu/+spec/foundations-n-dso-linking ?16:32
robbiewbarry: heh...but an early decision is ALWAYS preferred16:32
robbiew;)16:32
dokorobbiew: ok, I can add some ...16:32
cjwatsonlittle time> for which, UDD or python2.7?16:32
barryrobbiew: no doubt :)16:32
robbiewcjwatson: I believe python 2.716:33
barrypy2716:33
barryas default16:33
robbiewdoko: thnx16:33
barrycjwatson: oh, we didn't tell you?  we're making that change today. :)16:33
robbiewjhunt_: would also be nice to get some work items in http://blueprints.launchpad.net/ubuntu/+spec/packageselection-foundations-n-finish-upstart16:33
dokomy impression was that we had a decision to make 2.7 the default for natty16:33
robbiewbut I'm sure you and Keybuk will sort that ;)16:34
cjwatsonbarry: no complaints from this quarter16:34
dokoI'm just wondering when to do that switch16:34
Keybukthat's easy16:34
Keybuk[pitti] switch to systemd]16:34
barryif we can get all main packages !ftbfs by feature freeze16:34
cjwatsonbarry: actually, one complaint.  needs to be after alpha-116:34
dokowell, so make it the default after alpha1?16:34
barrycjwatson: that's why the smiley16:34
cjwatsonI wasn't sure :)16:34
barry:)16:34
cjwatsonis there any reason not to start on Friday, then?16:35
barrycjwatson: sorry, you mean make py27 the default and deal w/ the fallout?16:35
ScottKdoko: AFAIK we decided to get 2.7 fully supported and then see where we were timewise.16:36
jhunt_robbiew: sure - I've collated everything discussed at UDS and subsequently and it's a pretty big list if we attempt to implement all of it. I need to discuss implementation details with Keybuk.16:36
dokoScottK: when is this from your point of view?16:36
Keybukyeah, that's kinda the problem, it's a huge list :p16:36
robbiewjhunt_: ack...yeah, I imagine only a subset would be doable this cycle16:37
Keybukmy own attempts at writing are longer than yours16:37
ScottKdoko: From my POV if we get 2.7 fully supported prior to FF it should be default.16:37
Keybukand then I suffer from feature paralysis16:37
Keybukand FML etc.16:37
dokoScottK: that was not my question16:37
barryfeature freeze is 24-feb, alpha-2 is 3-feb.  i think *now* is not the time to switch, but let's make it a goal to switch at the rally16:37
ScottKOK.  What was your question?16:37
dokoScottK: *when* to switch?16:38
jhunt_robbiew, Keybuk: do we need to try and prioritize the list maybe to see what gives biggest bang-for-buck?16:38
cjwatsonthat's sort of why in the upstart UDS session I was trying to encourage figuring out things that could be passed out to multiple people, cherry-picking things that can be noticeable improvements for 10.10, etc.16:38
ScottKNot before we've done all the rebuilds and fixed FTBFS for sure.16:38
doko2.7 for 11.10 is too late. it's only a question *when* to switch for 11.04, not if16:38
cjwatsonsince I know that a giant list is hard to make progress on16:38
Keybukjhunt_: dunno, it's one of those things where I'm worried that I'm going to end up spending the entire cycle just planning16:39
robbiewjhunt_: well...I'd rather prioritize based on what's needed and also doable16:39
ScottKdoko: Then make the transition work get done smoothly and quickly and there will be nothing to argue about.16:39
robbiewjhunt_: like...I think even the idea about examples in the man page would be a good thing to have16:39
robbiewnot that flashy, but very nice to have16:39
dokoScottK: I'll make it as smoothly and quickly as the linking changes16:40
ScottKThat's what I'm afraid of.16:40
cjwatsonI'd honestly rather we just smashed through it between alpha-1 and the rally (or even between alpha-1 and Christmas)16:40
* robbiew is having dejavu...and recalls py2.6 by default16:40
jhunt_robbiew: I've almost completed 'init-examples' and it's coming along rather well I think. I'd rather have this info on the systems rather than (just) on the wiki to help out those in a disconnected environment.16:40
cjwatsonrather than waiting until everything is perfect, and missing the deadline16:40
robbiew+1 with cjwatson16:41
cjwatsonI would not take this stance if it looked as though we might not have time16:41
ScottKcjwatson: Are you on the python2.7 topic?16:41
cjwatsonbut does anyone not think that 2.5 months should be plenty?16:41
cjwatsonScottK: yes16:41
dokoin that case, I would like to make the test rebuild with 2.7 as the default, so we know immediately what needs to be fixed16:41
barrydoko: do it16:41
ScottKI think that's a great idea.16:41
barrycjwatson: i think 2.5 months should be plenty16:42
cjwatsonthen we should just get started on Friday, IMO16:42
cjwatsonesp. if somebody sends a mail to -devel-announce with details of what needs to change in packages16:42
barrycjwatson: well, in the ftbfs so far, there's no pattern16:43
dokoI can prepare something like this tomorrow16:43
ScottKdoko: You're going to rebuild everything, not just Main, right?16:43
dokoyes, but main gets priority16:44
cjwatsonbarry: ok, so no standard routine things?  doko said he wanted us to get away from symlinks for at least packages on the CD at the same time16:44
barrycjwatson: well, that's a bit controversial :)16:44
cjwatsonfor a smooth upgrade path in future16:44
mvobarry: oh? why?16:44
mvoisn't python2 the agreed future?16:44
cjwatsonthe controversy I know about is for packages sharing a namespace?16:44
barrybecause it entails changing the build systems on packages before debian does16:44
cjwatsoncan't we work with Debian to do that in experimental?16:45
barryand it does so w/o debian package maintainer input or approval16:45
cjwatsonI didn't say it had to be without input or approval ...16:45
ScottKcjwatson: It can.  We just need to do the work with Debian part.16:45
barrycjwatson: right, what ScottK says16:45
cjwatsonright.  I'm not saying we have to smash ahead with that with no forethought :)16:45
barrybut technically speaking, switching to dh_python2 is independent of making py27 the default16:45
cjwatsonfair enough16:46
dokoI would prefer it this way. just imagine that there may be packages where this is not possible16:46
barrywe should do both, but we also need to prioritize16:46
dokoI think 2.7 as the default should be the priority. we could handle the robustness even after feature freeze16:46
barryright.  we're agreed that dh_python2 is the future and we should work with debian package maintainers to get that transition going.  it's just not a blocker for py27 work16:47
barrydoko: +116:47
barrydoko: please do the test rebuild w/py27 as default.  that will give us some excellent data16:48
dokoso we'll have a busy next week ...16:48
barrybetter than boring :)16:48
* mvo actually would like to have a boring day again - just one 16:49
barry:D16:49
dokoyou'll have christmas16:49
barrymvo: hey, you have the forced vacation coming up16:49
robbiewok...changing gears16:50
robbiewgot 10min left16:50
robbiew[TOPIC] AOB? / Good News!16:50
MootBotNew Topic:  AOB? / Good News!16:50
dokonatty still boots (ix86 only), not arm16:51
barrypython 3.2 beta 1 comes out on saturday16:51
robbiewheh16:51
mvomini10 s-c startup time measurements work - bad news is that its slow16:51
robbiewthe mini10 or s-c? :P16:51
mvoand unity/compiz work on my natty box (after a word or two with the right people)16:51
barrywhich reminds me, doko: when b1 comes out, can we ditch py31 for natty?16:51
mvorobbiew: both! but the s-c part I hope to fix16:51
robbiewokey dokey16:53
robbiew#endmeeting16:53
MootBotMeeting finished at 10:53.16:53
robbiewthnx all16:54
ScottKbarry: I think it would be useful to support 3.1 and 3.2 both for Natty just to make sure we can do it.  It's not on any CDs yet, to it really doesn't hurt.16:54
mvothanks16:54
barryScottK: yeah, except all the good stuff (peps 3147 & 3149) is in 3.2 only16:55
dokobarry: no, no yet. and before making 3.2 the default I would like to wait for pep38416:55
barrydoko: i think you mean 382 (namespace packages).  i'm not optimistic that'll make it to 3.216:55
barry384 will *probably* make it.  i've seen lots of commits from mvl16:56
dokobarry: no, I mean the abi pep16:56
barryah, cool.  well, he has until saturday ;)16:56
=== jj-afk is now known as jjohansen
barryrobbiew: something tells me we're done <wink>17:01
ScottKbarry: [11:53:59] <robbiew> #endmeeting17:02
barryheh17:02
* ScottK thinks he knew already.17:02
barryokay, thanks then!  lunch awaits17:02
highvoltagegood afternoon everybody19:00
highvoltageJust finishing testing the alpha candidate for i386 and amd6419:02
highvoltagewe only had one build that actually kind of worked recently (2010-11-30), but luckily we had that one and at least we'll have an alpha release this time round19:02
highvoltageI found some nice Edubuntu videos that someone made yesterday, added it as favourites to the channel: http://www.youtube.com/user/edubuntuproject19:11
highvoltageat current rate we'll also hit the 500 fans mark on facebook this week. we haven't really promoted it much besides having a button for it on our website, and it's grown quite well over the last 2 months since it was started19:12
dindanice19:13
highvoltageEdubuntu council renewal is being dealt with by the CC, I was initially a bit worried that it might get stalled, but the CC is taking care of it. It's likely that the current EC will just be renewed, except for rich who stepped down19:14
highvoltagedinda: any updates from your side?19:15
dindanot really19:15
dindaholiday last week made it a short week19:15
highvoltageah yes, forgot about that19:17
highvoltagestgraber, mgariepy: anything from you that you'd like to share this week or is that it?19:18
mgariepynot for me19:18
highvoltageI guess that's that then. If there's more then we can take it to #edubuntu19:19
highvoltage*gong*19:19
barryhi folks, udd meeting about to start21:00
barry#startmeeting21:00
MootBotMeeting started at 15:00. The chair is barry.21:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]21:00
barry[TOPIC] agenda21:01
MootBotNew Topic:  agenda21:01
barryhttps://wiki.ubuntu.com/DistributedDevelopment/2010120121:01
poolie(hi all)21:01
barry[LINK] https://wiki.ubuntu.com/DistributedDevelopment/2010120121:01
MootBotLINK received:  https://wiki.ubuntu.com/DistributedDevelopment/2010120121:01
barrypoolie: hi21:01
barryi guess we'll wait a few minutes for folks to show up21:01
* jelmer waves21:02
* ajmitch_ is sort of caught up in stuff at work this morning21:02
barryajmitch_: cool.  thumper, james_w hi21:03
james_whey21:03
barryno slangasek?21:03
barrylet's get started then...21:04
barry[TOPIC] action items21:04
MootBotNew Topic:  action items21:04
barryreviewing from 2 weeks ago21:04
james_wslangasek is on vacation21:04
barryjames_w: ack21:04
barry   * barry to start some sphinx docs to be well-integrated w/ wiki.u.c (ongoing)21:05
barry 21:05
barrywe've been in discussion w/ dholbach and others about this re: updating the packaging guidelines.  i think the above action will fall under that initiative so i'm going to mark this one as done21:05
barryor at least take it off the list :)21:05
barry   * poolie to capture uds session notes in a wiki page, with more detail (turn it into a blueprint?)21:06
barry 21:06
pooliek21:06
pooliei didn't write anything more detailed about the uds sessions21:06
pooliei did linke to the transcript21:06
poolieand post about the survey results, after which there was some discussion21:06
poolieis more summary documentation of  UDS wanted?21:07
pooliei don't think it's a high priority now21:07
barryagreed.  the only thing left is to decide whether we want to add some work items to the blueprint21:08
jelmerpoolie: didn't you already send a brief summary to the list?21:08
barryjelmer: hi!21:08
jelmerhey Barry :-)21:08
pooliei can't recall if i did that before or after the previous meeting21:08
poolieso it's either done, or scratched off  :)21:08
=== JanC_ is now known as JanC
cdbsNow, which meeting is this?21:09
jelmercdbs: Ubuntu Distributed Development21:09
barrythe blueprint is here: https://blueprints.launchpad.net/ubuntu/+spec/other-foundations-n-distributed-development-review-and-planning21:09
barrypoolie: k21:09
* cdbs is a fan of UDD, so will watch around21:09
poolienext? ajmitch?21:10
barry   * ajmitch to come up with questions/topics for next meeting (re: REVU)21:10
barry 21:10
barryajmitch_: we can carry that one forward to the next meeting if you want21:11
barryi guess we will21:12
barry   * poolie to send bzr rotation pitch to platform mailing list21:12
barry 21:12
pooliestill to do; carry it over21:12
barrythx21:13
barrythat's it for action items21:13
barry[TOPIC] work items for blueprint21:13
MootBotNew Topic:  work items for blueprint21:13
barry[LINK] https://blueprints.launchpad.net/ubuntu/+spec/other-foundations-n-distributed-development-review-and-planning21:13
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/other-foundations-n-distributed-development-review-and-planning21:13
barryso we have this blueprint, and robbiew was pinging me about work items for natty.  i'm being kept pretty busy this cycle and sadly haven't had much time to circle back to udd work.  what can we realistically accomplish this cycle that we want to add to the blueprint?21:14
pooliei'm not quite sure what that means21:14
ajmitch_barry: apologies, in the middle of debugging something - next meeting would be good21:14
pooliethese are work items so that we can track how much effort we should/have expend?21:14
poolieor how much progress was made?21:15
barryi think robbiew is looking for work items that we can still accomplish in natty cycle21:15
barryright, so tracking effort yet to be expended21:15
poolieso after the survey and uds, there are two main things i want to do in the bzr team21:15
poolie- get network performance closer to apt-get source21:15
poolie(we should set a quanitifiable target, but i think we should do more investigation first)21:16
poolie- get the imports working more reliably21:16
pooliethose seem like things that would help and that are plausible for natty21:16
poolieperhaps they're too big/small/vague to be work items?21:17
barrywholehearted +1 for both21:17
barryprobably to big/vague, though great goals21:17
barrywell, network performance closer to apt-get source seems nearly work item-y21:18
barrymaybe with some percentage for "close"?21:18
pooliei think to make it specific and measurable we need to describe things more specifically21:19
jelmerpoolie: is there a specific way of fetching you have in mind to compete with apt-get source ? Is this for 'bzr co --lightweight' / 'bzr branch' / whatever is fastest ?21:19
pooliefor, someone with GbE to a source mirror there is no prospect we'll match it in the short term21:19
pooliejelmer, first looking for waste in simple branching atm21:19
poolieor an a lightweight checkout21:20
poolienext, a shallow checkout - john is doing code changes towards that21:20
barrypoolie: wasn't there some talk about trying to set up local mirrors of branches?  would that be more than just a fancy cron?21:21
poolieit wouldn't necessarily have to be more than that21:22
pooliemy inclination is to try to make the straightforward use faster first21:22
poolieperhaps we should look at doing it earlier?21:23
poolieit could be a big win but it also makes things a little more complicated21:23
barryit's hard for me to say.  bzr branch is not onerous for me, so it wouldn't be a huge win for me.  but for others it might be21:24
poolielet's leave that as a medium priority21:24
pooliei think there's a bug in udd discussing it21:24
barrywe can still add it as a work item though21:24
barryi think what you describe above could be condensed into other work items, at least for now (they can always change later).  i can take a shot at extracting that if you want21:25
barryand poolie you can decide later about resource allocation21:26
pooliecan you point me to a spec that is a good example of the right work item granularity?21:29
barryi'm not sure such a thing exists ;)21:29
barrybut hang on, let me see if i can find something close21:29
barryhttps://blueprints.launchpad.net/ubuntu/+spec/packageselection-foundations-n-robust-python-packaging21:29
barrythat one has gone through a few iterations, but sadly blueprint whiteboards have a history erase button21:29
poolieor no history at all, in fact?21:29
barryindeed21:29
poolieok i see21:29
poolieso this might help us keep track of things that don't match well to single bugs, or that aren't all in the same pkg21:29
barryyep21:29
pooliei'll see about adding them as we go along21:29
barryon the package importer failures, iiuc, we have very close to 2k failures, with some common problems.  perhaps a few work items there could be: categorize failures; make sure bugs are filed; fix top two common failures; reduce failures by 50%, etc.21:29
barrypoolie cool.  i'll leave that to you21:30
poolieat the moment we have something at a similar level on https://wiki.canonical.com/Bazaar/Plate21:30
barrywe also have a work item for moving that infrastructure into IS, right james_w?21:32
poolieright21:32
pooliethat progressed a bit, i think21:32
james_wyes21:32
poolieit's mostly gated on IS having time (in between midnight outages) to rebuild a machine for us21:32
barrycool.  should definitely add it as a work item to get credit for it :)21:32
barrywhat do you think about the other suggestions above?21:32
pooliei think those would be good steps21:33
=== bilalakhtar_ is now known as cdbs
pooliean item of getting it to zero might be elusive but we could have incremental steps21:33
barryyep.  i'll add those, and of course they can always be changed21:34
barryany other thoughts on the blueprint work items?21:34
poolieguess that's a no?21:35
barry[TOPIC] bugs of interest21:36
MootBotNew Topic:  bugs of interest21:36
poolieshould the list be roughly the length of things we expect to do before natty? or conservative, or optimistic?21:36
barryfor now it can be optimistic.  it's very easy to postpone, remove, change items as the cycle progresses, with really no penalty to do so21:36
pooliebecause we did this in detail last week, i propose this week just to talk about ones that changed or are interesting21:36
pooliek21:37
barrypoolie: +121:37
pooliehttps://bugs.launchpad.net/udd/+bug/653307 is, i think, understood, but needs to be finished21:37
ubottuUbuntu bug 653307 in Ubuntu Distributed Development "Import fails with missing referenced chk root keys" [Critical,In progress]21:37
pooliehttps://bugs.launchpad.net/bzr/+bug/603395 is fixed or nearly fixed?21:37
ubottuUbuntu bug 603395 in Bazaar "bzr commit in a heavyweight checkout does not propagate new tags" [High,In progress]21:37
pooliejames_w: are you here? any comments on redoing the imports affected by 653307?21:38
james_wI am21:38
* ajmitch hopes that the logging bot didn't get disconnected as well21:38
pooliehttps://bugs.launchpad.net/bzr/+bug/556132 is being worked on by exarkun, a twisted developer21:38
ubottuUbuntu bug 556132 in Launchpad Bazaar Integration "bzr: ERROR: paramiko.SSHException: Key-exchange timed out; consistent after sending 1GB data" [Medium,Triaged]21:38
poolieand i think that's all that's changed from that list this week21:39
james_wpoolie, was my comment in the bug unclear?21:39
poolieno, perfectly clear, thanks21:39
pooliejust wondered if anything happened after that21:39
james_wnope21:39
* barry has nothing to add21:39
pooliebut we should be able to do the checks and then ... i guess delete them from the package-import machine?21:40
poolieour SRU MRE was blocked and i think is now unblocked, so some fixes will get into maverick-updates in a few weeks21:40
barrythat would fix a nice handful of failures21:41
barry[TOPIC] AOB21:42
MootBotNew Topic:  AOB21:42
barryanything else not on the agenda?  any good news?21:42
pooliewe're having a hacking sprint at the platform rally21:42
james_wpoolie, you have to delete them from codehosting, and then clear out the info on package-import for them, and then retry21:43
pooliei think you all already know that21:43
poolieok, thanks21:43
poolieany other complaints or bugs?21:43
jelmerI added one to the list21:43
jelmerI'm not sure if it's appropriate for this meeting, it's not strictly useful for the way UDD works.21:44
jelmerI've been trying out recipes for a couple of different projects in the past few weeks. It's quite easy to set them up and stay working over time, but I'm finding that I have to go back often and update the version string and the source dependencies, something that could be automated.21:45
james_wyeah, version string is the biggest maintainence burden IME21:45
barrydo you think recipes are getting the publicity they need?21:46
poolieok21:46
pooliegood question21:46
pooliemaybe we should ask thumper to this meeting next time; he's been working a lot on them21:46
jelmerjames_w: Build-Depends is the other one for me, some of the packages I work with increase the versions of their dependencies regularly.21:46
* ajmitch saw recipes demoed live for the first time about 2 weeks ago21:46
poolieare they ready for wider pubilicity?21:47
barrypoolie: thumper *is* the lp stakeholder :)  but maybe this time sucks for him21:47
pooliethey seem to be growing organically21:47
james_wI would like to see the beta label removed, so that we can be more forceful in encouraging people to use them21:47
poolieit's about 11am for him21:47
ajmitchbarry: the meeting starts at 10AM for him, we're in the same timezone21:47
barryah, so i just need to ask flacoste bring the hammer down :)21:47
jelmerpoolie: They work well at the moment, though there've been a few breakages in the last two weeks.21:47
ajmitchsame city, for that matter :)21:48
pooliei'll find out, or send a mail or talk to him about what the path is to general availability21:48
barrypoolie: great, thanks21:49
barryanything else today?21:50
barry521:50
barry421:50
barry321:50
barry221:50
barry121:50
barry#endmeeting21:50
MootBotMeeting finished at 15:50.21:50
barrythanks everybody.  see you in 2 weeks21:51

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