/srv/irclogs.ubuntu.com/2008/08/29/#ubuntu-meeting.txt

=== C7878385 is now known as chalcedony
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 01 Sep 04:00: Arizona LoCo IRC | 29 Aug 15:00: Ubuntu Release | 02 Sep 15:00: Server Team | 02 Sep 21:00: Community Council | 03 Sep 17:00: QA Team | 03 Sep 20:00: Maryland LoCo IRC
=== C7477474 is now known as chalcedony
rismani want compile gcc 2.95.3 but i cant compile on ubuntu 6.1008:49
rismanhelp me!08:50
leoquant6.10 = eggy?09:03
leoquantnot supported anymore by ubuntu09:03
leoquantplease upgrade your system09:06
persiaWell, as importantly, this isn't the right place to ask for support, even when a given version is supported.09:07
stdinumm [08:51]* risman has quit ("http://www.mibbit.com ajax IRC Client")09:09
stdintoo late09:09
persiastdin: Indeed, far too late.  The two minute barrier is just as critical :)09:10
* e-jat brb .. zzZZzz sleepy .. 09:45
* e-jat back .. 09:46
=== tuxlinux_ is now known as tuxlinux
=== persia_ is now known as persia
nijaba@schedule11:20
ubottuSchedule for Etc/UTC: 01 Sep 04:00: Arizona LoCo IRC | 29 Aug 15:00: Ubuntu Release | 02 Sep 15:00: Server Team | 02 Sep 21:00: Community Council | 03 Sep 17:00: QA Team | 03 Sep 20:00: Maryland LoCo IRC11:20
=== dholbach_ is now known as dholbach
=== tuxlinux_ is now known as tuxlinux
NCommandergood morning all11:58
NCommander(or afternoon)11:58
norsettogood TOD11:58
NCommanderIt's almost time for the release meeting, no?11:59
TheMusoYes pretty much.11:59
NCommanderAny objection if I start it?12:00
norsettoNCommander: yes12:00
* NCommander doesn't start it then12:00
ScottKI'm here.12:00
norsettosistpoty|work: ?12:01
lagai'm here, too. the other mythbuntu guys are probably asleep so i'll be the mythbuntu representative.12:01
* ScottK looks around for sistpoty|work12:01
sistpoty|worksorry, was just at the restroom12:01
sistpoty|workshall I start?12:02
TheMusoOk lets get this show on the road.12:02
sistpoty|work#startmeeting12:02
sistpoty|workhm...12:02
sistpoty|work[startmeeting]12:02
NCommanderTHis isn't scheduled meeting is it?12:02
NCommanderWell, offically scheduled12:02
TheMusonot so much as its on the calendar etc.12:02
NCommanderWe've had issues starting xubuntu-dev meetings when we fall off the calendar12:03
NCommanderThat or the bot crashed again12:03
sistpoty|workok, let's do w.o. MootBot then12:03
persiaThe bot hasn't been responsive for the past couple days.12:03
sistpoty|workwelcome everyone to the motu-release meeting :)12:03
NCommanderThank you sistpoty|work12:03
NCommander;-)12:03
sistpoty|workanyone volunteering to write minutes?12:03
sistpoty|workif noone volunteers, I'd be up for it12:04
TheMusoNo, as I intend to pull myself from Ubuntu work after this meeting for a week.12:04
TheMusosorry12:04
NCommanderI'll do it if no one volunteers12:04
sistpoty|workok, thanks NCommander12:04
NCommanderI didn't see an agenda posted for this meeting12:04
ScottKThere isn't a formal one.12:05
sistpoty|workwell, it's pretty much in my head *g*12:05
NCommanderAnyone want to just recap whats on the floor so everyone is on the same page?12:05
ScottKThis is an organizational meeting.12:05
NCommanderoh12:05
sistpoty|workas it was just brought up on ubuntu-motu, let's start with motu-release <-> ubuntu-release12:05
sistpoty|workthere was the question, whether ubuntu-release may approve motu-release bugs, if there's need12:05
* siretart waves12:06
sistpoty|workwhich imo makes sense, what do you think?12:06
sistpoty|workhi siretart12:06
ScottKsistpoty|work: They've certainly done it in the past.12:06
TheMusoThats fine by me.12:06
ScottKI doubt we can convince them they aren't allowed to.12:06
* NCommander can't see an issue with it12:06
ScottKMy view is that they may, but they generally ought not.12:06
norsettosistpoty|work: I don't see a problem with that, supposed they really willing to take over ...12:07
siretartconsider packages in main with binaries in universe. that's for ubuntu-release anyway, no?12:07
sistpoty|worksiretart: imho yes12:07
TheMusosistpoty|work: agreed.12:07
ScottKOf course.12:08
sistpoty|workI guess the main use case is packages with MIR's pending (where I usually handed over to ubuntu-release anyways)12:08
sistpoty|workok, so we agreed on that one... what next12:08
ScottKObviously ubuntu-release must make the release as a whole work and if there's an urgent issue they need to deal with it.12:08
ScottKFreeze exceptions12:08
sistpoty|workScottK: yes, agreed12:08
ScottKI don't recall.  Did we do one or two ack's in Hardy?12:09
NCommanderI know offhand both mythbuntu and wine have requested standing freeze exceptions, are there any others?12:09
sistpoty|workok, how do we handle freeze exceptoins? two acks? one acks? different handling for upstream versions and new packages?12:09
NCommander(both had sFFes in hardy. It required two acks from -release)12:09
ScottKNCommander: I was going to go with standing exceptions next12:09
TheMuso212:09
NCommanderOh, my bad12:10
persiaI'd like to request that any universe flavour be permitted to shift selected software, etc. without a specific freeze exception.12:10
TheMusowe did 2 afaicr12:10
lagapersia: ACK12:10
TheMusopersia: seconded12:10
sistpoty|workpersia: what do you mean with "shift selected software"?12:10
norsetto212:10
ScottKpersia: Let's deal with exceptions after the basic process.12:10
persiaAlso tweak default settings, and the like.12:10
persiasistpoty|work: changes to seeds.12:10
sistpoty|workah, yes, sure12:10
lagapersia: and add new artwork ;)12:10
* ScottK gives up.12:11
persialaga: Well, that's covered under the ArtWorkDeadline, which I believe is separate.12:11
lagaindeed.12:11
sistpoty|workok, do we want to go with 2 acks again?12:11
ScottKlaga: But not if it has to go through the New queue.12:11
ScottKYes.12:11
TheMusoyes.12:11
ScottKpersia: I don't think there is one anymore.12:11
\shwhat is a universe flavour?12:11
norsetto+112:11
persia\sh: Xubuntu, Mythbuntu, Ubuntu Studio, Ubuntu Mobile, Ubuntu MID12:11
ScottKNevermind, there is.12:11
sistpoty|workok, so 2 acks it shall be12:11
* NCommander has some notes on seeds when we get there12:11
ograScottK, Artwork deadline is in about a month12:12
ScottKogra: Thanks.  Just looked.12:12
sistpoty|workogra: there is more than one artwork deadline actually *g*12:12
NCommanderThere were some recent changes w.r.t. to how seeds are being handled now. Not sure if -release is fully aware12:12
lagaScottK: i don't see what's wrong with getting new artwork thru NEW12:12
\shpersia: shrug12:12
cjwatsonFWIW our experience in core was that seed freezes were tempting but a waste of time12:12
ScottKlaga: Part of the reason for not allowing new packages is late in the release cycle is archive admins have stuff other than New to do.12:13
cjwatsonthey're not necessarily more disruptive than other code changes and might as well just be considered in the same light, i.e. whether they're internal changes or whether they actually introduce new features12:13
ScottKPersonally, I think each flavor with a seed needs to manage it.12:13
ScottKI don't see that as an issue for motu-release.12:13
sistpoty|workok, maybe we want to go straight to delegatoins?12:13
NCommanderScottK, that's happened. At least with xubuntu, we directly control our own seed now.12:13
lagaScottK: there are always exceptions. not allowing NEW packages because "archive admins have other stuff to do" is not exactly a good reason.12:14
sistpoty|workdo we want delegations again?12:14
ScottKlaga: Requiring one ask for an exception is not the same thing as saying none will be allowed.12:14
ScottKsistpoty|work: Yes.12:14
* sistpoty|work is also in favor12:14
lagaScottK: agreed. EOD.12:14
norsettosistpoty|work: definetively yes from me12:14
TheMusoagreed.12:14
\shif we can move those packages handled by the "universe flavour teams" out of the scope of the general motus, agreed...if they break something, we are not at fault...12:14
persiaAnd if they break something, their images fail, which tends to be a strong motivation to fix it.12:15
\shthat means, merging, syncing for the next release will only be work on by those teams, right?12:15
ScottK\sh: Not necessarily.12:15
ScottKIt just means they get to manage their own release process.12:15
sistpoty|workok, so what teams do we delegate to? iirc we had mozilla, kubuntu, desktop, mythbuntu and xubuntu in the last cycle... any team I forgot?12:15
raphink@schedule paris12:15
ubottuSchedule for Europe/Paris: 01 Sep 06:00: Arizona LoCo IRC | 29 Aug 17:00: Ubuntu Release | 02 Sep 17:00: Server Team | 02 Sep 23:00: Community Council | 03 Sep 19:00: QA Team | 03 Sep 22:00: Maryland LoCo IRC12:15
norsettosistpoty|work: didn't we have ubuntustudio too12:16
NCommandersistpoty|work, studio12:16
ScottKNot a team, but we also had WINE.12:16
TheMusoI'm expecting there to be a bit of activity as we settle the rt kernel.12:16
sistpoty|worknorsetto: right, I forgot that TheMuso handled studio12:16
sistpoty|work(as a delegate *g*)12:16
sistpoty|workany teams we should add to the list for this cycle?12:17
persiaubuntu-mobile-dev for Ubuntu Mobile and Ubuntu MID please12:17
ScottKI think KDE should definitely be delegated to Riddell.  He'll manage it for Main and it'd be silly for us not to let him deal with the whole thing.12:17
norsettoany reason actually to have wine having a standing exception?12:17
persiaAlso, Ubuntu-Studio-dev for Ubuntu Studio12:17
ScottKpersia: We need individuals.12:17
* ogra raises hand for ubuntu-mobile12:18
persiaScottK: OK.  _MMA_ for Ubuntustudio, ogra for ubuntu-mobile, lool for ubuntu-mid12:18
\shnorsetto: because you want the latest release always for wine...12:18
sistpoty|workwhat's ubuntu-mid?12:18
NCommandernorsetto, wine drops new updates every two weeks, and very few rdepends. Having a newer wine allows better windows software compatibility12:18
norsetto\sh:  why?12:18
persiasistpoty|work: Really small devices.12:18
lagasuperm1 and me for mythbuntu12:18
ograsistpoty|work, 4-7" devices12:18
ScottKsistpoty|work: Similar to mobile12:18
sistpoty|workah12:18
norsettoyes, thats also true for other packages, I don't see why wine is special12:18
ograScottK, totally different :) but yes12:18
laga(unless there are objections because i'm not a motu)12:18
sistpoty|workwhat about edubuntu? ogra do you have sets in universe?12:18
\shnorsetto: because with every release wine gets better, we have two week releases...and that needs to be handled ... wine has at least no rdepends and doesn't break anything else12:19
ograsistpoty|work, there is one metapackage LaserJock maintains12:19
ograsistpoty|work, bit the bigger amount is in main12:19
norsetto\sh: as I said, that true for., hmmm, 50% of universe packages?12:19
persia\sh: Wine does have rdepends.12:19
ScottKI think superm1 for mythbuntu12:19
cjwatsonsistpoty|work: "mobile internet device"12:19
siretartNCommander: I'm not sure I follow that argument, because if we did, we would have to update it every two weeks in -updates as well12:19
NCommanderThat was (roughly) the justification the original standing FFE was given last time around12:19
NCommanderI'm not saying it was right or not ;-)12:20
lagaScottK: i'd like to nominate myself, too. i've spent a lot of time inside these packages.12:20
persialaga: I think it's best one person per flavour, unless you think it oughtn't be cody-sommerville12:20
lagaalright.12:21
NCommanderThis is for seed managment?12:21
sistpoty|workok, ScottK suggested superm1 for mythbuntu... +1 from me12:21
laganot sure what cody-sommerville has to do with mythbuntu ;)12:21
\shpersia: oh well...I see...i wonder what is education-desktop-othger12:21
* NCommander got slightly lost12:21
\shother even12:21
sistpoty|worknorsetto, TheMuso, DktrKranz: superm1 for mythbuntu?12:22
ScottKI'm going to suggest that WINE should no longer get a free pass because it's past 1.0 now.12:22
TheMusoYes.12:22
persiaNCommander: For delegated approvals for seed-specific stuff.12:22
norsettoScottK: +112:22
NCommanderIf its xubuntu related, I can do it12:22
TheMusoScottK: I am enclined to agree.12:22
DktrKranzsistpoty|work, +112:22
\shcan someone ask yokozar ?12:22
norsettosistpoty|work: +112:22
sistpoty|workok, so superm1 for mythbuntu...12:22
NCommanderAgreed on wine, +112:22
TheMusoYes.12:22
siretartsistpoty|work: I'd like to nominate \sh and myself for updates to 'fai'12:22
sistpoty|workcody for xubuntu?12:22
ScottK\sh: If he wants an exception, I'm unlikely to say no, but I think he should ask.12:22
siretartsistpoty|work: and 'live-initramfs'12:22
norsettosistpoty|work: +112:23
ScottKsistpoty|work: Yes.12:23
TheMusocody for xubuntu yes12:23
\shScottK: na now that I see that other packages are stupidly depending on wine...12:23
sistpoty|workok, agreed on xubuntu/cody12:23
ScottKsiretart: Why does FAI need an exception?12:23
sistpoty|worklet's first discuss the remaining teams we already agreed on so far, ok?12:23
NCommanderHas anyone asked cody about handling approvals of seed related stuff? ATM, any xubuntu-dev can manipulate the seed now12:24
sistpoty|workkubuntu: Riddell? (and Riddell would you accept the delegation again?)12:24
ScottKNCommander: How he manages that is up to him.12:24
sistpoty|workagreed12:24
NCommanderok12:24
ScottKsistpoty|work: Definitely.12:24
NCommander+1 on Riddel for kubuntu12:24
ScottKasac for mozillateam12:24
TheMusoScottK: +112:25
sistpoty|workScottK: yep... asac also ok with the delegatoin?12:25
\shwhat about python-launchpad-bugs?12:25
ScottK\sh: What about it?12:25
DktrKranz\sh, isn't it in main?12:25
sistpoty|worklet's first discuss teams please... instead of single packages :)12:25
ScottKHistorically there have been very few per-package delegations.12:25
ScottKOK.12:25
\shoh good :)12:25
ScottKDid we cover all the teams?12:26
Riddellsistpoty|work: can do12:26
NCommanderWhat about xubuntu-eee, that's a different team from normal xubuntu12:26
sistpoty|workexcellent, thanks Riddell12:26
siretartScottK: I haven't merged the current svn yet. It doesn't make too much sense to merge it in the beginning of the cycle anyways12:26
TheMusowho did we decide for studio?12:26
ScottKNCommander: Is that a derivative for xubuntu then?12:26
persiaNCommander: It's not an official flavour at this point.12:26
ScottKTheMuso: You.12:26
sistpoty|workTheMuso: we didn't anything yet... do you want to handle studio again?12:26
TheMusoI'm not bothered either way, only that I won't be here for the next week.12:27
NCommanderOk, just making sure12:27
persiaI propose _MMA_ for approvals, unless TheMuso especially wants it.12:27
TheMusoI'm not bothered either way.12:27
ScottK_MMA_ then.12:27
sistpoty|work+112:27
TheMuso+112:27
sistpoty|worknorsetto, DktrKranz?12:28
DktrKranzno objections12:28
ScottKBefore we get off of teams, I think we also need to discuss what packages it covers.12:28
norsettosistpoty|work: sorry, I was distracted by another discussion12:28
lagaScottK: yes.12:28
sistpoty|worknp12:28
persiaScottK: There are more teams.  Can we cover the rest before we move to that?12:29
sistpoty|workwe still have -desktop12:29
sistpoty|work(at least)12:29
ScottKGnome has a standing freeze exception12:29
sistpoty|workfor hardy, I think it was policy to subscribe ubuntu-desktop, but I'd actually prefer an individual12:29
ScottKThat's from ubuntu-release.12:29
sistpoty|workScottK: but only core gnome-packages12:29
sistpoty|work(i.e. these that drop out of a gnome release)(12:30
ScottKOK.12:30
sistpoty|workwell, any suggestions?12:30
DktrKranzisn't a "gnome freeze exception" too free for sparse packages in universe?12:31
ScottKI think for those that get release in Gnome, it's covered.  For desktop packages in Universe, not in Gnome there is no exception.12:31
ScottKDktrKranz: It's packages released as part of Gnome, not all packages that use Gnome.12:31
persiaI think only if they are part of the official GNOME release.12:31
ScottKYes.12:31
ScottKSame for Riddell and KDE.12:31
DktrKranzah, thanks for the clarification12:31
norsettoScottK: so, should we assume all kde4- packages have a standing freeze exception or not ?12:32
sistpoty|workScottK: hm... actually I thought Riddell could handle any kde packages, wether these were part of kde or the surroundings (since he certainly knows best how these fit in)?12:32
ScottKsistpoty|work: For delegations, I agree.  For the standing freeze exception that I know KDE will need, no.12:33
sistpoty|workah, k12:33
ScottKI'd leave it to Riddell to decide if it's KDEish enough and approve it if he cares to.12:33
sistpoty|workagreed12:34
ScottKIt may be there's a person or two on motu-release who knows a little about KDE also.12:34
* sistpoty|work only uses it :P12:34
ScottKWe'll work on that.12:34
sistpoty|workok, back to gnome-desktop... do we want delegations, and if so whom?12:34
ScottKIsn't Keybuck the lead for that?12:35
DktrKranzseb128?12:35
ScottKPersonally I think we don't need it.12:35
persiaI thought pitti was the Desktop lead now.12:35
norsettosistpoty|work, scottk: wasn't that seb128?12:35
ScottKI've no idea.12:35
sistpoty|worknorsetto: certainly was... no idea if he still is though12:35
norsettolast cycle it was seb128 anyway12:35
Riddellseb128 is your man for gnome packages12:36
ScottKRiddell: Thanks.12:36
persiaAnyway, for Ubuntu Desktop, Ubuntu Server, and Edubuntu, everything ought be in main, so I don't see the rationale for motu-release delegation: surely that requires ubuntu-release attention.12:36
sistpoty|workok, agreed then, but we'll still need to ask him12:36
sistpoty|workubuntu-mobile?12:37
ScottKpersia: I know the KDE situation better.  In that case there are official KDE packages that we leave in Universe.  I'd imagine Gnome is the same.12:37
ScottKThat was ogra, right?12:37
sistpoty|work+1 for ogra12:37
persiaScottK: Ah, that makes sense then.  Objection withdrawn.12:37
TheMuso+112:38
ograyep, that was me12:38
DktrKranzif ogra is fine with it, +112:38
sistpoty|worknorsetto?12:38
* ogra is :)12:38
norsettoalso if ogra is not fine with it, +1 :-)12:38
ogralol12:38
sistpoty|workheh12:38
sistpoty|workubuntu-mid?12:39
ScottKogra: Will you be working out of the official repository this release or will you maintain something separate also?12:39
ScottKsistpoty|work: lool12:39
sistpoty|work+112:39
ograScottK, official only12:39
ScottKogra: Thanks.12:39
* ogra has never used PPAs for packages 12:39
ograi'm actually not a fan of separation :)12:40
sistpoty|workDktrKranz, TheMuso, norsetto: lool for ubuntu-mid?12:40
DktrKranzpersia, aren't you involved in -mid too?12:40
TheMuso+112:40
ograDktrKranz, as he is in mobile12:40
norsettosistpoty|work: +112:40
sistpoty|workand lool: would you accept the delegation?12:40
ograDktrKranz, persia is involved in *everything* ;)12:40
persiaDktrKranz: Yes, but I'm not on a release team.12:41
DktrKranzheh :)12:41
DktrKranz+1 for lool for -mid as well12:41
norsettopersia aka the Ubuntu deus-ex-machina12:41
ScottKI have to go wake up my daughter.  Back in two.12:41
sistpoty|workok, any other team that I forgot right now?12:41
ograyeah, he has root on all your machines ... beware12:41
* sistpoty|work is scrared *g*12:41
persiasistpoty|work: Did you do -server?12:42
sistpoty|worknope12:42
persiaDo you want to do -server?12:42
loolsistpoty|work: I do12:42
DktrKranzthere are several packages in universe, AFAIK12:42
sistpoty|workso what about -server? imo it's covered by ScottK, but I wouldn't necessarily mind a delegation12:42
sistpoty|workthanks lool12:42
DktrKranz(for -server)12:42
DktrKranzso, if server team has plans for some of them, a delegation should be granted12:43
loolwin 1012:43
loolUps12:43
sistpoty|workTheMuso, norsetto: server-team? if so, suggestions?12:44
ScottKIf you all want to delegate, I'm OK with it.12:44
DktrKranzmathiaz could do the job, if he agrees12:44
TheMusoI don't know who to suggest, but I'm ok with deligations.12:44
sistpoty|workDktrKranz: -112:44
ScottKI would object to Mathiaz12:44
sistpoty|workdue to recent incidents *g*12:44
norsettosistpoty|work: whats better than good old ScottK12:44
sistpoty|worknorsetto: +1 for ScottK12:44
DktrKranzah... ruby...12:44
ScottKI'm not convinced we need a server delegate, but if others feel the need, I don't object.12:45
* siretart has to agree with ScottK that the ruby issue wasn't handled very ubuntu-like. at least not what I would expect from someone who signed the CoC12:45
norsettosiretart: pls. lets not start this here ...12:45
sistpoty|workScottK: /me doesn't have a preference, as you'll handle it either way ;)12:45
sistpoty|workDktrKranz, TheMuso, norsetto: so ScottK as delegate, or motu-release for server?12:46
sistpoty|work(or s.th. else=12:46
persiaI don't see the point of assigning a delegate who is also motu-release.12:47
persiaLet's skip server.12:47
norsettosistpoty|work: I said it already, scottk all the way12:47
TheMusoIf ScottK is up for it, thats fine by me, thats if he thinks the server team needs deligations.12:47
ScottKpersia: It means I don't need ack #2.12:47
persiaAh, then it is worth a vote :)12:47
DktrKranzI'm fine with ScottK, motu-release hat is not a blocker, IMHO12:47
sistpoty|workotherwise TheMuso would be out *g*12:48
sistpoty|work(for studio)12:48
sistpoty|workok, then ScottK/ubuntu-server12:48
sistpoty|workmore teams?12:48
DktrKranzsistpoty|work, if persia had motu-release, he's out for *everything* :)12:48
sistpoty|workhaha12:49
norsettoDktrKranz: be aware, He is taking notes12:49
sistpoty|workScottK: you were questioning about package sets of delegations, right?12:49
ScottKYes.12:49
sistpoty|workgo ahead then ;)12:49
ScottKAs an example, the myth packages are important to mythbuntu, but they are not the only user.12:50
sistpoty|workok, I guess if there's a certain amount of overlap, it's better that motu-release coordinates, what do you think?12:50
ScottKFor Xubuntu, I think we delegate xfce and xubuntu specific packages, but not necessarily every single package they seed.12:50
ScottKYes.12:50
ScottKIn the last cycle, there was a myth specific excption that was granted by motu-release.12:51
TheMusosounds ok to me12:51
sistpoty|workI usually did ask the affected teams anyway last cycle for input12:51
ScottKSo for mythbuntu it's packages specific to them.12:51
ScottKFor xubuntu, it's xubuntu packages and xfce412:52
ScottKFor Studio it's there specific packages and ???? - not sure what12:52
ogra.oO(what *are* xubuntu packages ? seeded ones ?)12:52
ogra(or mobile in my case)12:52
ScottKTheir meta-packages, artwork, the like.12:52
persiameta, settings, artwork, etc. ?12:52
_MMA_-rt12:53
ogranot the ones that are only used n their seeds as well ?12:53
sistpoty|workwell, I assume that delegates will ask back if unsure, so I'm not too sure if need to come down to specific package sets12:53
ScottKI'd like to ask the delgatees what they think it should cover.12:53
* ogra would like to cover all packages that are only explicitly in his seed 12:53
ScottKogra: Perhaps, but not if you aren't the only one that has it seeded12:53
ograright12:53
ograthen motu-release needs to apply12:53
ScottKogra: Could you generate a list of what that covers?12:53
sistpoty|workoh, damn... I must run in 7 minutes :(12:54
ogranot right away yet, but i can do one, yes ... we should probably all do that12:54
ScottKGenerically, I'd like to see each delegate give us a list of what they think they've got covered12:54
ScottKYes.12:54
ograyeah12:54
NCommandersistpoty|work, I may have to run before this meeting is over, if so, I'll read the logs and write the notes when I get back12:54
sistpoty|workScottK: sounds like a nice idea..12:54
_MMA_Rough list: https://wiki.ubuntu.com/UbuntuStudio/PackageList12:54
lagaScottK: for mythbuntu, we'll need everything in the mythbuntu-* namespace, anything involving mythtv and stuff like xmltv12:54
sistpoty|workat least it would avoid confusion whom to ask12:55
sistpoty|workNCommander: kk12:55
ScottKlaga: We'll have to argue over that a bit then since you aren't the only interested party with mythtv, but we needn12:55
ScottKneedn't do it now12:55
* DktrKranz needs to go right now, read the log12:55
persiaRight.  Perhaps delegates could reply to the mail including the meeting minutes with an explicit list of packages they are asking to be able to approve?12:55
ograright12:55
persiamotu-release could then approve or amend the list?12:55
TheMusosounds good.12:56
ograor suggest changes12:56
_MMA_But it doesn't need to be everythng. Off the top of my head I'd say anything ubuntustudio-*, -rt kernel Ardour and JACK are usually ones that need love in past cycles.12:56
lagaScottK: same argument applies to xubuntu - they aren't the only ones interested in xfce.12:56
persialaga: Let's not argue specifics here.  Just submit the list, and see what can be approved.12:56
ograwe should probably discuss that on the ML ... i would think the team that *mostly* uses them might also be a valid case12:57
lagaokay.12:57
_MMA_sure12:57
sistpoty|workok, agreed on the lists thingy12:57
ogralaga, i.e. i might like dvb-utils in mobile at some point ... but i'd happily leave decisions for that to mythbuntu12:57
ScottKI'll be back in about two minutes12:58
ScottKKeep going12:58
sistpoty|workok, what else do we need to cover?12:58
norsettowifeys is calling for luch, gotta go12:58
lagaogra: i dont think dvb-utils sees that many changes :) and it's not like people want to break stuff. IMHO it's about taking care of packages you know well without having too much bureaucracy12:58
lagabut that's a bit OT now12:59
ograwas just an example :)12:59
* ogra has a conf call now ... but will lurk12:59
sistpoty|workstanding freeze exception process?12:59
* lool same as ogra 12:59
sistpoty|workhow about a mail to ubuntu-motu and at least three ubuntu-release membes giving a +1 to grant one? other ideas?12:59
sistpoty|works/ubuntu-release/motu-release/13:00
sistpoty|workdamn, gotta run as well :(13:00
TheMusosistpoty|work: sounds good13:00
TheMusoi will reply when I return from my holiday.13:00
sistpoty|workTheMuso: have fun!13:01
ScottKFine with me.13:01
sistpoty|workoh, personal side note: I'll be on vac during next week as well...13:01
ScottKPer package delegations is next.13:02
sistpoty|workScottK: can you take over hosting, as I need to go now?13:02
ScottKOK.13:02
sistpoty|workthanks13:02
ScottKI'm not convinced we have a quorum anymore for decision making.13:02
ScottKI'd suggest anyone who feels a need for a per-package delgation mail the MOTU ML and we'll discuss it.13:03
TheMusoI agree.13:04
ScottKOK.  Anything else?13:04
james_wI have a suggestion13:04
james_wwell, two13:04
ScottKYes?13:04
ScottKI have something else too13:04
ScottKI propose we get rid of the diffstat requirement in freeze exceptions.  It's pretty meaningless.13:05
ScottKjames_w: Go ahead.13:05
james_wfirstly, I think having a clear policy within the team about how a member should put a hold on a particular freeze exception while more discussion happens, or something similar, is a good idea.13:05
james_wand perhaps extending that to how people outside the team might be able to do that.13:06
ScottKGenerally we've done that by needing +2 but not approving if any motu-release member had an objection.13:06
ScottKAnd if others have input, I don't think we'd ignore that an press on.13:07
siretartjames_w: like in 'writing 2-3 sentences risk analysis' for each requst?13:07
james_wwell, there was an incident last cycle where a couple of members were unhappy that a change was uploaded while they felt their concerns were still outstanding13:07
TheMusoScottK: +1 for removing the need for diffstats.13:07
james_wmaking it clear what should happen should help avoid that.13:08
ScottKFair enough.13:08
siretartScottK: the diffstat shows that the requester did take a look at the diff13:08
ScottKsiretart: I think it shows they know how to run the diffstat command.13:08
ScottKActually looking is a different issue.13:09
james_wI think asking for an overview of the changes and an assesment of the risk is far more effective at showing that, and far more useful13:09
ScottKI know this is something cjwatson had a strong opinion on.13:09
cjwatsonoh god yes13:09
cjwatsonnamely, please get rid of the diffstat requirement, it's never been useful :)13:09
ScottK+113:09
siretartScottK: well, it still makes it more obvious at once how big the changes are. but maybe we are too lax anyways with granting exceptions to large changes so they've become meaningless already13:09
cjwatsonin fact in some cases it's been counterproductive because people send the diffstat rather than the diff :)13:10
siretartoh13:10
ScottKI think having something about risk assessment is more useful.13:10
cjwatsonif release team members want a diffstat it's surely not difficult to run it themselves; they need to glance over the diff anyway13:10
cjwatsonif a release team member is approving things without looking at the diff then they aren't doing their job right, imo13:10
siretartk13:10
ScottKI remember the other thing we need to discuss ...13:11
ScottKDo bugfix only releases need an exception?13:11
ScottKWe experimented with not last time and I think it worked well.13:11
james_wI think it's reasonable, but I think you need more -release members to discuss it13:14
persiaI like having a bug for those, whether a special ACK is required or not.13:14
ScottKWhich is what we did last time13:15
ScottKSo we can take it to the ML13:15
ScottKAre we done then?13:15
persiaRight.13:15
* ScottK says the meeting is over.13:15
persiaDid you get enough votes to squelch diffstat, or will that need to be discussed at the later meeting as well?13:15
TheMusoOk thanks folks. See you all in 10 days or so.13:16
ScottKpersia: I'm going to believe that I did.13:19
persiaScottK: OK.  Let's hope it makes the minutes.13:19
* persia thinks diffstats are actually useful.13:19
=== asac_ is now known as asac
loolw00t15:54
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Ubuntu Release Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 02 Sep 15:00: Server Team | 02 Sep 21:00: Community Council | 03 Sep 17:00: QA Team | 03 Sep 20:00: Maryland LoCo IRC
loolslangasek: Are you chairing the meeting today?16:02
mdzslangasek: hello?16:07
mdz#startmeeting16:07
mdzMootBot: :'-(16:07
loolYeah, broken16:07
slangasekmm, sorry16:07
slangasekmorning :/16:08
slangasekno MootBot today?16:08
mdzafraid not16:08
loolhttp://paste.ubuntu.com/41581/ agenda16:08
mdzlet's charge ahead though16:08
* slangasek nods16:09
mdzwould be good to have hyperlinks in the agenda for the bug lists16:09
lool(Mootbot is broken for a couple of ubuntu-mobile meetings)16:09
slangasekare folks here?16:09
mdzdavidm and pgraner are here, just spoke to them16:09
mdzcjwatson is on a phone interview16:09
mdzheno_ connected a moment ago16:09
heno_hi16:09
loolScott is on leave I think16:10
mdzyes16:10
loolas well as pitti16:10
mdzmissing dendrobates?16:10
davidmI bugged the scribes about mootbot yesterday16:10
loolI saw Hobbsee some hours ago I think, but she's offline right now16:10
slangasekyes, Hobbsee let me know she wouldn't be able to make it16:11
slangasekand I think that accounts for everyone16:11
loolScottK was invited as well16:11
looland Riddell16:12
slangasekRiddell is also on leave, I believe; ScottK: there?16:12
loolHere he is16:13
mdzwe have a quorum; let's get started16:13
slangasekagenda, with links: http://paste.ubuntu.com/41584/16:14
mdzbug 255635 pitti was working on, but he's not back from holiday until Monday I think16:15
ubottuLaunchpad bug 255635 in sysklogd "Kernel messages not logged to /var/log/kern.log" [High,Triaged] https://launchpad.net/bugs/25563516:15
slangasekthe list of known blockers is short, but we have two among them that currently don't have assignees16:15
mdzbug 250506 is is milestoned but not assigned to anyone16:16
ubottuLaunchpad bug 250506 in consolekit "shutdown and restart buttons do nothing" [High,Confirmed] https://launchpad.net/bugs/25050616:16
slangasekI can try to look at 255635 today, and pass it back to pitti again if I don't get through it16:16
mdzthere are also 3 critical bugs on https://bugs.edge.launchpad.net/ubuntu/intrepid/+bugs (not on the agenda, but should be)16:16
slangasekI think 250506 was seb's/pitti's area, both of whom are currently out16:17
loolAgreed on #250506, and as it's quite security sensitive, pitti is the right person IMO16:17
slangasekok; I'll assign 250506 to pitti16:18
loolWe could either revert to GDM doing shutdown/reboot, or allow everybody to shutdown/reboot via dbus as upstream does, or find a creative solution16:18
loolI suspect the former will happen as it might take a while to sort out16:18
slangasekcjwatson: the last bug on there is yours, bug #254042 - any concerns there?16:19
ubottuLaunchpad bug 254042 in germinate "debootstrap does not install apt with --variant=buildd for intrepid chroot" [High,Confirmed] https://launchpad.net/bugs/25404216:19
cjwatsonno concerns but I haven't made progress yet, as it were16:20
* slangasek nods16:20
slangasekok, moving to https://bugs.edge.launchpad.net/ubuntu/intrepid/+bugs as mdz pointed out16:21
slangasekthere are three bugs listed as critical there: bug #197680, bug #253076, and bug #24737616:21
ubottuLaunchpad bug 197680 in xserver-xorg-video-ati "rotation doesn't work with this board using Screen Resolution" [Critical,Confirmed] https://launchpad.net/bugs/19768016:21
ubottuLaunchpad bug 253076 in linux "No X with current kernel (downgrade fixes it)" [Critical,Triaged] https://launchpad.net/bugs/25307616:21
ubottuLaunchpad bug 247376 in fglrx-installer "undefined symbols when trying to load fglrx" [Critical,Triaged] https://launchpad.net/bugs/24737616:21
slangasekbug #197680 appears to have been considered fixed already, and was reopened last week16:22
ubottuLaunchpad bug 197680 in xserver-xorg-video-ati "rotation doesn't work with this board using Screen Resolution" [Critical,Confirmed] https://launchpad.net/bugs/19768016:22
slangasekI'll follow up with bryce about that today16:23
loolbug #253076 looks fixed in .2716:23
ubottuLaunchpad bug 253076 in linux "No X with current kernel (downgrade fixes it)" [Critical,Triaged] https://launchpad.net/bugs/25307616:23
lool"16:23
lool"Seems to be fixed in .27-116:23
tseliotbug # 247376 depends on the fact that (currently) the fglrx driver doesn't work with the new Xorg ABI16:23
tseliot#24737616:24
loolI understand that fglrx for intrepid might land post intrepid16:24
slangasekright, bug #253076 is tentatively resolved, contingent on 2.6.27; we'll come to that later16:25
ubottuLaunchpad bug 253076 in linux "No X with current kernel (downgrade fixes it)" [Critical,Triaged] https://launchpad.net/bugs/25307616:25
tseliotlool: yes, this is likely. superm1 can you comment on this?16:25
slangasekin any case, that's not something we can set an alpha-5 timetable for16:26
slangasekunfortunately16:26
loolBryce also said on ubunu-devel that AMD had based work on 2.6.26 rather than .27, but as fglrx now builds against linux 2.6.27 in Ubuntu that should be ok16:26
loolI don't think we can do anything for alpha 5 except sit and wait for a new fglrx; perhaps something to mention in the known bugs?16:26
slangasekyes, good point; adding an ubuntu-release-notes task16:27
tseliotwe should do it for the 2 nvidia legacy drivers affected by the same problem too16:28
tseliot(96, 71)16:28
slangasekthere are a significant number of other high-importance bugs on that list without milestones; I don't think we need to go through those individually right now, I'll go through the list myself afterwards to find any that need to be milestoned16:29
slangaseklet's move on to talking with the teams, about any would-be-blockers they have that aren't on that list16:29
slangaseklool: would you care to start?16:30
mdzthe list of high-importance bugs targeted for intrepid might be a good source of would-be blockers as well16:30
loolslangasek: Sure16:31
slangaseker, yes - I meant, any would-be blockers that aren't already milestoned16:31
loolSo concerning mobile, we now have daily images being built daily for the mid seed16:31
loolThe mid seed is the intrepid seed for hardy's mobile seed16:31
loolThe images are around since a couple of days and have many technical issues, but it's good to have something to test and work on now16:32
loolThe major things to land are the installer16:32
loolEmmet is still working on tweaking Ubiquity and we will include his work before alpha 516:32
loolAnother major thing is 2.6.2716:32
slangasekcjwatson: I'm assuming that it's best to leave you 'til last since you're on a phone call now, shout if you become available sooner16:33
loolWe're using the linux-lpia source package, which is still at 2.6.2616:33
mdzlool: are the test images for the Q1 Ultra?16:33
loolI'm experiencing issue with our dailies which point at the kernel (apt-get update hangs), so .27 might be worhthwhile16:33
slangasekare the ubiquity tweaks on-track to be in the archive before Tuesday (milestone freeze)?16:33
loolmdz: You can boot the image in kvm and the Q1, but it's super ugly; Xorg wont come up without fixing the upstart event for instance16:34
lool(fixed this morning)16:34
pgranerlool: is assistnace needed from the kernel team to help get you to .2716:34
loolslangasek: I would have to check with persia; we basically set a hard deadline on having an installer before alpha 516:34
loolslangasek: I'll confirm with him that he knows about the deadline16:35
slangaseklool: ok; if those aren't going to be done by Tuesday, please keep the release team informed, since that will impact ISO building16:35
loolpgraner: I've proposed a phone call between Michael Frey and Amit next week16:35
loolpgraner: I've summarized our dilemma on ubuntu-devel@; basically we asked Intel for .26 drivers and still haven't got any16:35
slangaseknext week> so linux-lpia to .27 is looking like post-alpha-5?16:35
pgranerlool: we need to revisit that amit is on other things, I'll join the call in his place16:36
loolIn all cases, it's likely we aim at using whatever intrepid uses as a kernel number16:36
loolpgraner: Ok; we need to discuss security support of linux-lpia for the intrepid cycle too; will include you when I setup the meeting next week16:36
davidmwe may have issues for the poulsbo drivers however, trying to sort that out.16:36
pgranerlool: ack16:36
pgranerdavidm: eta on that? need anything from us?16:37
loolslangasek: linux-lpia .27 should be decided after next week's call with Intel was my proposal; this week's call didn't help us in any way sadly16:37
slangasekok16:37
davidmpgraner, I'll catch you off line, to review possible steps16:37
pgranerdavidm: ack16:37
slangaseklool: are there any particular ubiquity bugs that I should add to my milestoned list?16:37
davidmpgraner, no eta, working with Intel16:37
loolFinally, the other major things we need to land for mobile are some new source packages, most in NEW or REVU pending upload to NEW16:38
loolAll mobile specific naturally16:38
loolIn terms of feature, we didn't yet decide of which IM and mail client we would include; I pushed modest and we didn't push the pidgin-maemo fork which are the main candidates, versus thunderbird and empathy ATM16:39
loolslangasek: No particular ubiquity bugs that I know of16:39
loolslangasek: My understanding is that Emmet's work is around simplifying the installation procedure, and fitting the UI on the small screen16:39
* slangasek nods16:40
loolThese are the main things for mobile, so quite a lot as you see; we're generally a bit late in the cycle16:40
ogramdz, as soon as the ubuntu-mobile image is built, bug #261873 is fixed and ubiquity is there you can test ubuntu-mobile on the Q1 as well16:41
ubottuLaunchpad bug 261873 in xf86-input-evtouch "make evtouch devices work with hal-input in intrepid" [High,Triaged] https://launchpad.net/bugs/26187316:41
loolOh right there's also the evtouch issue on the Q116:41
looland ath5k doesn't work on the Q116:41
slangasekfwiw, unless there've been more uploads since yesterday, I believe all your NEW packages have cleared the queue now16:41
ograright16:41
looleven with .27, according to ogra's testing16:41
ograi'll attack evtouch mid next week16:41
ograand i'm supposed to file the ath5k bug before end of my workday today and connect with rtg for that16:42
loolslangasek: I see my uploads were cleared; don't know when the other NEW packages were pushed exactly16:42
slangaseksounds like we've pretty thoroughly covered mobile then, and everyone knows what's on their plate; anything else before moving on?16:42
loolOh soryr forgot that we also have to select media player16:42
ogranote that most/many of your NEW packages are universe16:42
loolNo NEW package invoved though as moblin-media isn't an option so far16:43
ogra(so migth not actually be on steves radar)16:43
loologra: (good point)16:43
ScottK-laptopAnd motu-release has delegated authority for their respective areas to lool and ogra so in Universe they control their own destiny.16:43
loolslangasek: Ok to move on16:43
slangaseklool: since you're the emergency contact for the desktop team this week too :), do you have anything on that front?16:44
loolOne thing I'd like to mention is the Gtk+ screen flicker issue16:44
lool#245383 I think16:44
loolbug #24538316:44
ubottuLaunchpad bug 245383 in xserver-xorg-video-nv "Screen flickers when loading applications" [Undecided,Invalid] https://launchpad.net/bugs/24538316:44
loolIt's quite annoying as it causes a delay on startup and will cause your screen to go black and  light again16:45
mdzthere are a variety of GNOME crashers (gnome-power-manager and gvfsd-trash come to mind) which seem fairly important but I don't see on the bug lists (they are reported though)16:45
loolThe issue is also relatively deep and the proposed fix is to add xrandr API which will take a long while16:46
loolI guess we might revert gtk+'s changes on this area, but I'm not sure how easy taht is16:46
loolmdz: Could you please bump them to >= high?16:46
slangasek245383 is milestoned, but doesn't have anyone assigned (beyond "desktop")16:46
slangaseklool: do you know who would look into the GTK flicker problem?16:47
mdzlool: bug 252174 is already high16:47
ubottuLaunchpad bug 252174 in gvfs "gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch()" [High,Triaged] https://launchpad.net/bugs/25217416:47
loolI don't have much time to work on it before alpha 5  :-/16:47
mdz46 duplicates!16:47
* ogra has seen it as well already16:47
mdzprobably deserves an apport dupe filter16:47
loolslangasek: I guess to revert the gtk changes could go on seb128's plate if he doesn't mind, but I didn't check when he comes back16:48
nizarus@schedule tunis16:48
ubottuSchedule for Africa/Tunis: Current meeting: Ubuntu Release 02 Sep 17:00: Server Team | 02 Sep 23:00: Community Council | 03 Sep 19:00: QA Team | 03 Sep 22:00: Maryland LoCo IRC16:48
loolProbably too late16:48
slangasekseb128 is back Monday, I believe16:48
mdzthe gnome-power-manager one I am thinking of most closely matches bug 149746 but that's very old16:48
ubottuLaunchpad bug 149746 in gnome-power-manager "gnome-power-manager crashed with SIGSEGV in g_closure_invoke()" [Medium,Triaged] https://launchpad.net/bugs/14974616:48
loolI've had gnome-settings-daemon crash on me a couple of times, but as a heisenbug already reported with some dups16:49
slangasek... which is pretty standard, so assigning it to seb128 wouldn't be worse than assigning it to anyone else; should I do so, or do you want to talk with seb first?16:50
ogratedg is the g-p-m maintainer16:50
loolPlease assign to seb and mention that I can help on the issue16:50
slangasekassigned16:52
* k0p is away: I'm busy right now16:52
slangasekbug #252174 escalated; with 46 dupes, we should try to get that out of the way for alpha-516:52
ubottuLaunchpad bug 252174 in gvfs "gvfsd-trash crashed with SIGSEGV in g_main_context_dispatch()" [High,Triaged] https://launchpad.net/bugs/25217416:52
slangasek... if I can pick the right milestone from the pull-down, that is16:53
slangasekmdz: should a new bug report be filed about the g-p-m crash, or do you think 149746 is the same bug?16:53
mdzslangasek: I have a crash file for what I saw; it looked sufficiently similar that I didn't file a new one, but since it's happening to me constantly, I don't think it's the same16:54
mdzI will file a new bug with the crash report when I'm at home where the crash file is, and drop you a note with the bug number16:55
slangasekmdz: ok, thanks16:55
mdz(though I'm curious if I'm the only one with a spastic g-p-m)16:55
slangasekany other high-profile desktop bugs?16:55
looldunno whether I should be reporting on specs progress again; I mentionned that the fast-user-switch-applet IM and session integrations landed, but IM doesn't work properly for me16:56
slangasekwas just about to ask about specs :)16:57
ogramdz, i didnt have issues yet ... so might be HW or settings specific16:57
slangaseklool: are you still working with tedg on those IM issues, then?16:57
loolI was asked to work on better-login-speed intrepid-menus-review as time permits16:57
slangasekneither of those are alpha-5 material, I guess16:57
loolslangasek: I think he reproduces; he received all my complaints and knew about the most important ones already16:58
loolslangasek: I understand that he will address them ASAP, but we didn't discuss any alpha 5 deadline for them16:58
slangasekyou and I talked about intrepid-device-permissions, I think that was already mostly done before pitti went on vacation and I fixed the last PAM bit this week16:59
loolI find the red button icon ugly when you startup a fresh intrepid image for instance, because there's no IM running at all16:59
* slangasek nods16:59
loolOne personal desktop thing I'd like to land before alpha 5 is an elisa update17:00
lool0.5.x series17:00
loolI have to finish reviewing the packaging and push them, I hope today or this WE, just after I get an ack on a FFE17:01
slangasekyes, you mentioned that to me earlier; is a FFe bug filed?17:01
loolNot yet17:01
loolWill do just after the meeting17:01
slangasekok17:01
slangasekanything else, or should we move on?17:01
loolFinally, now that I have a webcam I can pick the cheese update17:01
loolWe still are on 2.22 cheese and miss many new features developped during gsoc17:02
mdzslangasek: let's move on, this is starting to drag17:02
loolI was the casual cheese sponsor, tremolux was doing the packaging updates; sadly he has been busy or on holiday17:02
slangasekdendrobates: hi17:02
dendrobatesslangasek: hi17:03
slangasekdendrobates: what news in the land of servers?17:03
ScottK-laptopslangasek: I can generally speak to Kubuntu status if you want it.17:03
dendrobateswe would really like to get bug 261847 taken care of.17:03
ubottuLaunchpad bug 261847 in openjdk-6 "Installing openjdk-6-jre-headless pulls in dbus/avahi" [Critical,Confirmed] https://launchpad.net/bugs/26184717:03
slangasekScottK-laptop: let's pick that up after server team17:04
slangasekdendrobates: I believe I saw some uploads in connection with that?17:04
slangasekor were those uploads to make other packages use -headless?17:04
mdzdoko doesn't seem to be online17:05
slangasekdoko is also on holiday this week, until Monday17:05
dendrobatesslangasek: part of the problem was fixed, but at least, as of yesterday, this still existed.17:05
slangasekdendrobates: has someone spoken with doko about this directly yet?17:05
dendrobateswe also have a serious regression in likewise-open, bug 26226417:06
ubottuLaunchpad bug 262264 in likewise-open "Fails to join a domain: Unknown pam configuration" [Critical,Confirmed] https://launchpad.net/bugs/26226417:06
dendrobatesslangasek: yes, but we haven't reached an agreement yet.17:06
slangasekright, that'll be tied to the new pam framework landing17:06
dendrobatesslangasek: yes, Jerry is working on it now.17:06
slangasekdendrobates: ok, so it's more than just a question of whether doko will have time to work on it Monday, even17:06
dendrobatesslangasek: we can do it, it is really, wheter he will agree to it or not.17:07
slangasek261847 is milestoned to alpha-6, which looks like the right target under the circumstances17:07
mdzslangasek: doko is not back until Tuesday17:07
slangasekoh, indeed17:07
mdzperhaps someone else should have a look17:07
lool(What's the rationale for having the mdns recommends?)17:08
dendrobatescjwatson is aware of this as well.17:08
slangasekmdz: well, it appears to be a design decision rather than a straightforward bugfix; do we have anyone other than doko who would make such decisions for openjdk?17:09
slangasekdendrobates: it'd be really great if we could get likewise using the new pam framework; feel free to point Jerry my way on that17:10
mdzslangasek: punt to cjwatson17:10
slangasekmdz: ok17:10
dendrobatesslangasek: already did.  :)17:10
dendrobateswe also have landscape-client that is almost done with it's security review.17:11
slangasekdendrobates: any other bugs to be escalated, or "unsettling" changes between now and the milestone?17:11
dendrobatesslangasek: no.17:11
slangasekok.  you and I can discuss landscape-client status offline/as-needed; let's move on so we can stay within time17:12
slangasekpgraner: kernel?17:12
pgranerslangasek: sure17:12
slangasekoh, sorry17:12
slangasekbacking up17:12
slangasekScottK-laptop: kubuntu?17:12
ScottK-laptopThe big thing for Kubuntu is KDE 4.1.1 was released this week.17:13
ScottK-laptopIt's being packaged now and we plan to push it on Monday.17:13
ScottK-laptopSo that should be a bit interesting.17:13
ScottK-laptopThe only major bug issue I'm aware of is Knetworkmanager not working with networkmanager right now.  I think Riddell was looking at it.17:14
slangasekwell, looks like kubuntu ISOs currently have plenty of space to grow, so at least that's not a concern :)17:14
ScottK-laptopWe updated the remaining KDE bits in Intrepid to 3.5.10 this week.17:14
ScottK-laptopPublished the full suite to hardy-backports with only a few minor regressions reported and none that relate to packages that are still KDE3 in Intrepid17:15
ScottK-laptopI think that's it.17:15
ScottK-laptopOn a personal note 3.5.10 was the first time I've packaged an entire KDE release all by myself.  That was interesting.17:16
slangasekScottK-laptop: thanks for the update17:16
slangasekpgraner: kernel :)17:17
ScottK-laptopYou're welcome.17:17
cjwatsonok, sorry I couldn't make it until now17:17
pgranerslangasek: sure (one more time :-) )17:17
pgraner2.6.27 Call for Testing (CFT) went out yesterday. So far we've been tracking upstream regressions [LINK http://bugzilla.kernel.org/showdependencytree.cgi?id=11167&hide_resolved=1]17:17
pgranerIn addition to Regressions reported by our users [LINK https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-2.6.27] they are tagged with regression-2.6.27 for easy searching17:17
pgranerBugs in 2.6.26 and prior that are fixed by 2.6.27 are tagged with fixed-2.6.27 [LINK https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=fixed-2.6.27]17:18
pgranerNew 2.6.27 bugs are tagged with linux-2.6.27 [LINK https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=linux-2.6.27]17:18
pgranerThe fallback plan in the event of everything going south is documented here: [LINK https://wiki.ubuntu.com/KernelTeam/2.6.27-kernel-plan]17:18
pgranerSo far the worst regression from 2.6.26 is https://bugs.edge.launchpad.net/ubuntu/intrepid/+source/linux/+bug/25307617:19
ubottuLaunchpad bug 253076 in linux "No X with current kernel (downgrade fixes it)" [Critical,Triaged]17:19
pgranerSuspend/Resume failures17:19
slangasekare the incompatibilities with third-party drivers also being tracked as "regressions"?17:20
mdzpgraner: and bug 262539 of course ;-)17:20
ubottuLaunchpad bug 262539 in linux "2.6.27 REGRESSION, hangs during boot while preparing restricted drivers" [High,New] https://launchpad.net/bugs/26253917:20
pgranerslangasek: other than the nvidia/fglrx no17:20
slangasekok; but those two are?17:20
pgranerslangasek: we are tracking them but they were broke in some form or fashion in 2.6.26 so we are not calling them "regressions" to 2.6.27, we are tracking tho.17:21
slangasek253076> seems to be a bug that was a regression in /2.6.26/, and is fixed in 2.6.2717:21
slangasek(as mentioned earlier)17:22
pgranerslangasek: it would appear so on 25307617:22
mdzand it's tagged fixed-2.6.27, not regression-2.6.2717:23
* pgraner nods17:24
mdzI'll test a couple of laptops with 2.6.27 over the weekend and see what happens17:24
heno_the fallback plan looks workable to me from a QA perspective17:24
slangasekI notice that on <https://wiki.ubuntu.com/KernelTeam/2.6.27-kernel-plan>, fglrx/nvidia are not listed as decision criteria17:24
mdzheno_: what about the 2.6.27 certification test?17:24
slangaseknor is there mention of certification test17:24
* ogra can report 253076 fixed on his laptop17:24
heno_I have a call with pgraner after this meeting to coordinate beefing up hardware testing in our labs with .27 and have discussed it with Marc also17:24
pgranerslangasek: certification is working after this meeting, will be updated once a plan is decided17:25
ogra(with .27)17:25
heno_we are planning specific push on that17:25
slangasekmdz: I guess the 'linux-2.6.27' tag made it show up on the list of "new 2.6.27 bugs"17:25
pgranerslangasek: Given we don't have much control over nvidia/fglrx I'm not sure we want to use that as decision criteria17:26
heno_We need to run more comprehensive tests on all the machines (autotest, LSB etc) and see what falls out17:26
slangasekwell, I think we need to have our eyes open to the consequences of not treating nvidia/fglrx as a blocker17:27
heno_and also make sure the kernel team has easy access to machines for debugging and testing17:27
pgranerheno_: ack on that17:27
ograslangasek, and communicate that well in advance and very loud this time ...17:27
slangasekthat's not something I look forward to being in the middle of trying to communicate17:28
loolrelease notes task again?17:28
ograwell, we shoudl do better than we did for the 8.04.1 hardy issues i mean17:29
ograwhich imho was not loud enough as the footnote we had put in17:29
slangasek... I'm not looking forward to the binary driver support turning into an 8.10.1, either17:30
ograindeed ...17:30
mdznext?17:31
cjwatsonI guess that can be me17:31
cjwatsonfeature freeze exceptions raised by my team were:17:32
slangasekcjwatson: go ahead17:32
cjwatson * new pulseaudio to match new alsa and new kernel17:32
cjwatson * experimental python 3 packages (not by default, maybe not really FFe)17:32
cjwatson * system-cleaner (tonight, I'm told)17:32
cjwatson * usb-installer-images (ditto)17:32
cjwatson * dvd-performance-hacks (ditto)17:33
cjwatson * timezone map changes for ubiquity17:33
cjwatson * openoffice.org 3 (again, not by default, parallel-installable)17:33
cjwatson * xorg-options-editor needs promotion to main I think17:33
cjwatsonand I think that's about it17:34
mdzfreeze exceptions should probably be a standing agenda item from here on out17:34
loolpulseaudio> I understand git's version carries plenty of fixes; wouldn't it make sense to simply push that before alpha 5 to get more testing and revert to the current version if it's too borken?17:34
cjwatsonas others have said, the fglrx issue is a major one. I'm told that the devprivates rework in the X server has left fglrx with a bit of catching up to do17:34
mdzhas fglrx been screwed twice, by X and kernel?17:34
cjwatsonmdz: yes17:34
mdzfantastic17:35
cjwatsonlool: only thing is that Luke's on holiday next week17:35
cjwatsonI was told that 2.6.27 would "add to the risk", and I think that was posted on the -devel thread17:35
mdznext year, let's everyone go on holiday at the same time, it would be much more convenient17:35
loolThat's actually what happens in August in France *cough*17:36
cjwatsonseveral people mentioned 261847. doko is caught between a rock and a hard place here; he had (semi-legit) release-critical bugs filed in Debian when it was the other way round, because Java's network resolver was unable to resolve names without libnss-mdns17:36
mdzcjwatson: unable to resolve names *at all*?17:36
cjwatsone.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47721117:36
ubottuDebian bug 477211 in ia32-sun-java6-bin "ia32-sun-java6-bin: Cannot resolve domain names" [Grave,Open]17:36
cjwatsonyes. I have no idea why17:36
cjwatsonI think that is a bug but simply dropping the recommendation to a suggests does not seem like the obviously right fix17:37
cjwatsonso I am very reluctant to overrule doko in his absence, and would rather wait 'til he gets back17:37
loolIsn't it because using system's nsswitch.conf in a 32-bits jvm which couldn't find libmdns?17:37
mdzthat bug looks like it's probably specific to biarch, no?17:38
cjwatsonin http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=430917 Aurelien said "The 64-bit version should also depends on libnss-mdns. If it is not installed you get the exact same error."17:39
ubottuDebian bug 430917 in libc6-ie86 "Java programs fail in name resolution." [Important,Closed]17:39
cjwatsonI haven't ripped my system apart to test, but Aurelien isn't someone I'd automatically mistrust17:40
loolHe might mean the 64 bits version in a 32-bits system?17:40
cjwatsonhe might, but that wasn't the implication I drew17:40
mdzwe can't debug it here, but it seems like this would benefit from a closer look17:40
mdzperhaps even before matthias gets back17:40
slangaseklet's pick that up on #ubuntu-devel after, then17:41
cjwatsonit's a one-day delay, and as slangasek said alpha-6 does not seem an unreasonable target for this. I agree that it's intrepid-critical to resolve but don't see that it's alpha-5-critical17:42
slangasekcjwatson: so for xorg-options-editor, is "x-kit" the package in need of promotion?17:42
cjwatsonthat and screen-resolution-extra I think17:42
slangasekneither appears to have MIRs going yet?17:43
cjwatsonI asked bryce to file those but looks like he hasn't yet17:43
cjwatsonI'll remind him17:43
slangasekok17:43
slangasekheno_: QA?17:44
heno_Our smoke testing found some problems with OEM mode. It seems to work on Ubuntu now, but there is still an open bug on Kubuntu (#251634). See: https://wiki.ubuntu.com/Testing/DailySmoke17:44
* slangasek targets17:45
heno_Other than that, we have concerns about the kernel SRUs we will get after Intrepid is out17:45
slangasekin general / as a perceived consequence of 2.6.27?17:45
heno_as noted, I'll have some talks with pgraner about the .27 process17:46
* slangasek nods17:46
heno_slangasek: the latter, we are scheduling an SRU before release here17:46
heno_though we often have kernel SRUs post release anyway, but I was hoping to reduce that17:47
ograwasnt that reduced by the new policy ?17:47
heno_anyway, we'll monitor it over the next few weeks17:47
slangasekok17:48
slangasekanything else you've noted that should be alpha-5 critical?17:48
heno_not that I'm aware of17:48
mdzwe need to see hardware test results very soon17:48
heno_agreed. It's on my urgent list17:49
mdzthanks17:49
slangasekScottK-laptop: anything for motu-release?17:49
ScottK-laptopWe had a good organizational meeting this morning.17:50
ScottK-laptop4 of 5 are returning from Hardy, so the team's in good shape.17:50
cjwatsonon 251634, I could do with help from a KDE developer17:50
slangasekinterleaving a bit, since we're over time: ISO size has been stable and very good, the last round of reductions made a big difference17:50
ScottK-laptopThe hot ticket at the moment is that it seems there are some developers who might have rushed to upload stuff before FF.17:50
cjwatsonI'm not sure how much of the stderr spew there is actually fatal17:50
cjwatsonrushed> just like every other Ubuntu freeze :)17:51
ScottK-laptopRushed yes, but rushed some things that appear to have been particularly unfortunate.17:51
ScottK-laptopSo we're looking into it.17:51
Riddellcjwatson: the oem stuff is on my todo to look at, I can try and look next week17:52
cjwatsonta17:52
slangasekScottK-laptop: FFe process under control for you guys at the moment?17:53
ScottK-laptopyes.17:53
ScottK-laptopWe're repeating mostly what we did for hardy and doing a lot of delegation to experts.17:53
* slangasek nods17:53
ScottK-laptopWe're also repeating the idea of continuing to allow new upstreams that are only bugfix.17:54
ScottK-laptopNo other news.17:54
slangaseksounds good17:54
slangasekok, items left on the agenda17:54
slangasek * Hardware testing17:54
slangasekthat's been discussed above17:54
slangasek * Future issues expected to impact the release (e.g. major upstream changes pending)17:55
slangasekI /hope/ those have all been covered by this point, if not please contact me ASAP after the meeting to discuss :)17:55
slangasek  * status of issues found in previous milestone17:55
slangasekI'll go through those myself after the meeting, to not hold people up, and escalate any that still need attention17:55
slangasekanything else, or shall we adjourn?17:56
slangasek#endmeeting17:57
slangasekthanks, folks!17:57
mdzslangasek: do you maintain a list of those (future upstream issues) somewhere?17:57
loolBye17:57
slangasekmdz: not currently; I don't think there's been any carry-over from previous milestones, but I'll review the previous logs to confirm, and can make a point to add any that do carry over to the agendas18:00
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 01 Sep 04:00: Arizona LoCo IRC | 02 Sep 15:00: Server Team | 02 Sep 21:00: Community Council | 03 Sep 17:00: QA Team | 03 Sep 22:00: Platform Team | 04 Sep 13:00: Desktop Team
=== C5478548 is now known as chalcedony
keffie_jayxj #openbravo21:33
keffie_jayxupssss21:33

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