/srv/irclogs.ubuntu.com/2008/11/19/#ubuntu-meeting.txt

=== bazhang_ is now known as bazhang
gmarzioz#geologia01:31
Tm_Tok01:35
=== maxzda is now known as [mz]
=== [mz] is now known as _mz_
=== Joint_ is now known as TiMiDo
=== dholbach_ is now known as dholbach
mvo@berlin10:08
juliux@schedule berlin10:14
ubottuSchedule for Europe/Berlin: 19 Nov 18:00: QA Team | 19 Nov 19:00: Platform Team | 20 Nov 13:00: Ubuntu Mobile Team | 20 Nov 14:00: Desktop Team | 21 Nov 21:00: Tunisian LoCo Team IRC | 25 Nov 17:00: Server Team10:14
juliux;)10:14
inetpro@schedule Johannesburg11:28
ubottuSchedule for Africa/Johannesburg: 19 Nov 19:00: QA Team | 19 Nov 20:00: Platform Team | 20 Nov 14:00: Ubuntu Mobile Team | 20 Nov 15:00: Desktop Team | 21 Nov 22:00: Tunisian LoCo Team IRC | 25 Nov 18:00: Server Team11:28
inetpro@schedule Pretoria12:01
ubottuError: Unknown timezone: Pretoria - Full list: http://tinyurl.com/4vyvp812:01
=== njpatel is now known as njpatel_away
=== thekorn__ is now known as thekorn
=== njpatel_away is now known as njpatel]
=== njpatel] is now known as njpatel
robbiewhi all :)15:59
TheMusoHey robbiew.15:59
cjwatsonafternoon16:00
* cjwatson skates his activity report in just in time, whoops16:00
evandhello16:00
robbiewheh16:00
liwhey16:00
liwoh, activity report *blush*16:00
robbiewcjwatson isn't the only one ;)16:00
robbiewdon't worry...I probably won't get to reading them to later this afternoon16:01
james_whi all16:01
cjwatsongood example and all that16:01
robbiewmultiple back-to-back meetings today...whoopee!16:01
robbiewI'm showing slangasek at Lexington today, so not sure if he's showing up16:02
slangasekif I can keep track of the clock16:02
slangasekmorning16:02
robbiewdoko, mvo: joining?16:02
robbiewslangasek: :)...aren't timezones fun?16:03
slangasekyes!16:03
TheMusorobbiew: Too right they are. :p16:03
dokorobbiew: online16:03
robbiewdoko: good evening sir...thanks!16:03
robbiewsuppose I should start it16:04
robbiew#startmeeting16:04
MootBotMeeting started at 10:04. The chair is robbiew.16:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:04
robbiew[TOPIC] Alpha 116:05
MootBotNew Topic:  Alpha 116:05
robbiewforgot that on the agenda :P16:05
robbiewfigure we should at least mention it16:05
cjwatsonslangasek may have stuff to mention there, I certainly do16:05
slangasekI see d-i has been uploaded, but ubiquity hasn't yet16:05
cjwatsoninstaller is now merged so theoretically we are ready to go with initial build testing; just doing an initial alternate CD build now16:05
cjwatsonevand is on ubiquity, I think ...16:05
slangasekI think that's the main blocker; there's some kubuntu uninstallables that Riddell is working on16:06
cjwatsonI suspect that there will be some early failures16:06
* slangasek nods16:06
cjwatsonthe GTK d-i frontend is merged and built but known broken16:06
cjwatson(fails to boot with some inscrutable error message)16:06
cjwatsonI'll need to dig into that, but probably not for alph a116:06
evandja, partitioning is broken in ubiquity.  I'm trying to get to the bottom of it.16:06
cjwatsonhm. not a surprise I guess. ping me if you need a hang16:06
cjwatsonhand16:06
evandnoted, thanks16:07
cjwatsonwe could go for alternate-only, and indeed that might be sensible?16:07
cjwatsonwe've done that in the past16:07
=== kirkland` is now known as kirkland
cjwatson(and server)16:07
slangasekthat would be fine, if that's where we are16:07
slangasekno sense in dragging out the milestone freeze for stuff that's just Not Ready Yet16:08
cjwatsonthis is way earlier than we've ever done an alpha 1 before, as I've observed elsewhere16:08
robbiewright...it is just an Alpha16:08
cjwatsonso I don't feel bad about it being partial16:08
cjwatsonparticularly with armel consuming energy as well16:09
dokoarmel already looks better than hppa =)16:09
cjwatson:-)16:09
TheMusoThats not hard. :p16:09
slangasekheh16:09
robbiewanything else on this topic?16:10
robbiewonce...16:10
robbiewtwice...16:10
robbiewgone!16:10
robbiew[TOPIC] UDS16:10
MootBotNew Topic:  UDS16:10
robbiewSo I'm trying to at least organize blueprints for the roadmap items16:11
robbiewand then we need address any other ideas from the team16:11
slangasekis there a reference for the roadmap?16:12
slangasek(URL)16:12
cjwatsononly internal at the moment, https://wiki.canonical.com/UbuntuPlatform/Roadmaps/9.0416:12
cjwatsonthere's also some stuff linked off wiki.u.c/FoundationsTeam16:12
robbiewthnx16:12
* slangasek nods16:13
robbiewyeah, I plan on creating at list of our specific blueprints for the public wiki as well16:13
robbiewyou can see them all at https://blueprints.launchpad.net/sprints/uds-jaunty16:14
robbiewwith the schedule located here: http://summit.ubuntu.com/uds-jaunty/16:14
* mvo is here, sorry for being late16:15
dokook, I should add one ... python will be fun this cycle16:15
robbiewnp16:15
robbiewperfect timing16:15
* mvo is confused "19 Nov 18:00: Platform Team" <- according to topic?16:16
cjwatsonif you already have ideas for the blueprints robbiew has created, there's no harm dropping them into a clearly-marked section at the end of the spec now16:16
cjwatsonmvo: the fridge calendar is ... not exactly 100% accurate sometimes16:16
cjwatsonI'll mail ubuntu-news-team after the meeting to get it corrected16:16
mvothanks!16:16
robbiewmvo: discussing UDS session topics...you had some good ideas16:17
* mvo should have used his google calendar16:17
mvoalpha-1> I enabled release-upgrades for it "update-manager -d" should work16:17
mvouds topics> python is going to be interessting, I would be interessted in porting my stuff to python2.6 (to prepare for 3.0)16:18
cjwatsonlikewise16:18
liwI'd be interested in helping port Python stuff to 2.616:19
* mvo has a terrible long list of ideas16:19
dokoI'm almost sure that I can't do this alone16:19
robbiewone thing to keep in mind for this release, is the bug fixing effort...so we have to be mindful of how much feature work we plan for16:20
mvoone of the cool things that came up recently in debian is screenshots.debian.net - it would be cool if we could discuss something like this at uds and maybe talk to the debian people behind it16:20
dokoanother: please have better interaction for archive rebuilds / ftbfs packages during the release cycle16:20
cjwatsondoko: indeed I think it would be unwise for you to try to do so - half the point of python 2.6 is to get people used to the newer constructs they need to use, isn't it?16:21
dokocjwatson: well, 2.5->2.6 looks easier than 2.4 -> 2.5. there are some source changes needed (new keywords, but these are fairly simple to solve)16:23
cjwatsonhas_key becomes deprecated IIRC16:23
cjwatsonfoo.has_key(bar) -> bar in foo16:23
cjwatson(which you can do in 2.x anyway of course)16:24
mvo"with" becomes a keyword16:24
cjwatsoncan we aim for only 2.6 on the CD for jaunty?16:24
dokoyes, trying ...16:24
liwis zope still 2.4 only?16:24
dokozope216:24
liwoh, but it's not on the cd, never mind16:24
cjwatsonif you're using "with" as a variable name, mind you, I think that's a little odd :)16:24
dokobut should we care about it?16:24
mvodoko: how much is C api going to change (if at all)?16:24
dokonot that much, its better than the 2.5 change16:25
* mvo nods16:25
robbiewok...assuming that discussion is done :)16:27
robbiewanything else regarding UDS planning?16:27
mvocan we still add topic suggestions to the wiki? or is it too late now?16:28
robbiewnot too late...but getting close16:28
mvook, thanks16:28
robbiewI'm thinking Friday should be the last day16:29
robbiewwith a short week in the US coming up...then another with FOSSCamp16:30
robbiewneed to get the Specs started16:30
robbiewok...next on the agenda is bugs16:30
robbiew[TOPIC] Bugs16:30
MootBotNew Topic:  Bugs16:30
robbiewdon't think there's much to cover here16:30
slangasekis "hotkey madness" explicitly on the UDS schedule anywhere?16:31
cjwatsonI gave robbiew the usual bug links16:31
* TheMuso remembers seeing stuff re acpi/power management... I think16:31
cjwatsonjaunty alpha 1 is https://bugs.launchpad.net/ubuntu/jaunty/+bugs?field.milestone%3Alist=220916:31
slangaseknot power management, just hotkeys...16:31
cjwatsonjust the one there16:31
cjwatsonslangasek: yes, it's on https://wiki.ubuntu.com/FoundationsTeam/UDS/December200816:32
slangasekok16:32
mvowhat does "EPR" mean?16:33
cjwatsonwhere's that?16:33
mvohttps://bugs.edge.launchpad.net/ubuntu/jaunty/+source/update-manager/+bug/28440816:33
robbiewwhere do you see that?16:33
ubottuLaunchpad bug 284408 in update-manager "r3xx Hardware does not work with fglrx [EPR#257839]" [Medium,In progress]16:33
cjwatsonI think it might be an AMD code16:34
cjwatsoncheck with bryce16:34
mvoaha, thanks16:34
cjwatsonyes, bryce said: "This issue has been forwarded to AMD as EPR#257839."16:34
robbiewprobably their internal bug tracking16:34
liw"external problem report" perhaps?16:34
robbiew;)16:34
robbiewok, so for bugs...the usual...watch yours and any hot ones that come across16:35
* mvo will take care of the update-manager one16:36
cjwatsonthere are one or two of https://bugs.launchpad.net/ubuntu/jaunty/+bugs that are worth cleaning up anyway16:36
robbiew[TOPIC] Sponsorship Queue16:36
MootBotNew Topic:  Sponsorship Queue16:36
cjwatsonI'll take the lintian one16:36
cjwatsonand maybe klibc if I have time16:36
robbiewk, thnx16:37
* TheMuso got onto main-sponsors yesterday so will be able to more actively help out with sponsoring, so far as cleaning up bugs on the queue goes.16:37
* liw still can't sponsor anything, but is going to apply for UCD tonight/tomorrow16:37
cjwatsonyeah, it's time to get back into the sponsorship queue now that merges are nearly out of the way16:37
robbiewcool..thnx sir!16:37
slangasekI've been less than effective at sponsorship this week (i.e., didn't get any done)16:37
robbiewjames_w is a sponsoring beast!16:38
cjwatsonslangasek: I think you have an excuse, being in Lex16:38
slangasekI suppose :)16:38
robbiewyep, agree16:38
robbiewok...moving right along16:39
robbiew[TOPIC] Activity Reports16:39
MootBotNew Topic:  Activity Reports16:39
robbiewI haven't had a chance to review all of them yet...since most came in today :P16:40
robbiewanything anyone wants to mention here?16:40
robbiewthat CAN be mentioned here ;)16:40
cjwatsonI wanted to mention http://people.ubuntu.com/~ubuntu-archive/architecture-mismatches.txt as another tool for archive admins16:40
cjwatsonit's empty at the moment because I dealt with it :)16:40
cjwatsonbut it reports problems where overrides have got out of sync between architectures for some reason, which happens occasionally due to Soyuz bugs16:41
slangasekI'm sure I'll forget that url... is it linked from somewhere?16:41
cjwatsonI'll put it on the wiki if I can remember where the other *-mismatches are listed16:41
slangasekok :)16:42
cjwatsonArchiveAdministration I guess16:42
slangasekor https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#Consistency16:42
cjwatsonnone of the other *-mismatches were there though16:43
cjwatsonI put it on ArchiveAdministration but feel free to add it elsewhere16:43
slangasekok16:43
cjwatson(under "Useful web pages")16:43
cjwatson[that's all from me]16:44
robbiewheh...shouldn't they all be "useful"?16:44
robbiewthat's all for me as well16:45
robbiew[TOPIC] AOB16:45
MootBotNew Topic:  AOB16:45
robbiewanything else folks want to cover?16:45
cjwatsongood news: I found a way to ditch 3MB+ of data from the CD ... bad news: I think I might want to add the GTK d-i frontend, which is 10MB+16:45
cjwatsonmaybe I'll only add it on the server CD for the moment, which has plenty of space16:46
cjwatsonalso, lots of people here should be well able to help out with fixing misc build failures in the armel port in progress16:46
cjwatsonas doko said it's actually doing reasonably well with uninstallables at the moment, but still several more to fix16:46
cjwatsonif you're interested, hop onto #ubuntu-arm16:46
* mvo joins16:47
cjwatsonyou don't necessarily need hardware, I don't have any16:47
TheMusocjwatson: If you could give me a heads up as to what needs to be done seed wise for the gtk installer, I am happy to look into putting things in place for studio to use it as well.16:47
dokoI tagged some of them ftbfs-armel16:47
mvocjwatson: how do you test it, do you use qemu-system-arm?16:47
mvowhat kind of failures are that usually?16:47
NCommandermvo, you can't use qemu-system-arm out of the box16:47
cjwatsonTheMuso: will do once I work it out myself; no great rush since it doesn't actually work yet16:47
dokoand please ping a buildd admin to rescore fixed builds16:47
NCommanderIt doesn't target new EABI ARM16:47
cjwatsonmvo: a number of the failures are reproducible on i386, and only haven't bitten it because we haven't rebuilt the package in question for a while16:48
cjwatsonor reproducible if you set up some special situation, or obvious for some other reasson16:48
cjwatsonreason16:48
ogramvo, if you need something tested, feel free to poke me16:48
NCommandermvo, or me16:48
ograor NCommander :)16:48
mvoexcellent!16:48
cjwatsonI think there are three people on #ubuntu-arm now who've confessed to having a working bootstrap16:48
NCommanderWe're making excellent progress, we cleared gtk's build-deps, and I kicked mono and fixed it last night16:49
cjwatsonit's all very early port days, exciting if you're a weirdo like me who happens to enjoy that kind of thing ;-)16:49
* mvo thinks that sounds like fun, but having a VM with a "real" arm system would be even more fun :)16:50
* NCommander loves porting work16:50
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: QA Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 19 Nov 18:00: Platform Team | 20 Nov 12:00: Ubuntu Mobile Team | 20 Nov 13:00: Desktop Team | 21 Nov 20:00: Tunisian LoCo Team IRC | 25 Nov 16:00: Server Team
liwis there going to be a qemu-system-arm that works out of the box?16:50
NCommanderI feel like I'm back on Debian :-P16:50
cjwatsonwe should have access to a bit more hardware soon, hopefully involving a porting box in the DC16:50
NCommanderliw, no, but I can merge the arm eabi patches into our QEMU, but they're still somewhat experimental16:50
TheMusoA porting box would be good.16:50
dokocjwatson: I think we should disable the debian archive soonish (e.g. once the kde stuff can be built)16:51
cjwatsonwe're just a bit short of hardware right now16:51
cjwatsondoko: I agree, really needs infinity to get back though16:51
cjwatsonwhich I think is soon16:51
cjwatsonwe'll get by for the moment, I think16:51
NCommanderdoko, I have a patch to clear the KDE FTBFS, I'm simply watching to make sure I haven't broke i386/amd64 first16:51
dokoNCommander: very nice!16:51
NCommanderdoko, I did this for m68k ;-)16:51
NCommanderWe've got X11's build-deps cleared; I won't be suprised if we can install ubuntu-desktop relatively soon16:52
dokoNCommander: then please fix gnat and openjdk for m68k as well ;p16:53
TheMusoAs soon as pulseaudio has its libltdl weirdness sorted out at least.16:53
NCommandergnat on m68k requires a bootstrap, I already did one, but I had trouble getting the actual Debian packages to compile once I candian-crossed the compiler16:53
NCommanderopenjdk has an in-progress port, it needed some helper functions16:53
NCommander^- doko16:54
liwI think we're running out of time16:54
robbiewyep..anything else?16:55
robbiewonce...16:55
robbiewtwice...16:55
robbiew#endmeeting16:55
robbiew:)16:55
MootBotMeeting finished at 10:55.16:55
dokorobbiew: well done for the first meeting :0)16:55
evandthanks!16:56
robbiewthanks!16:56
liwthanks16:56
TheMusoThanks,16:56
mvothanks16:56
robbiewdoko: thanks :)16:56
NCommanderI should sit in on more foundation teams meetings, its an interesting experience16:56
james_wthanks all16:56
robbiewlol16:57
robbiewNCommander: glad you enjoyed it16:57
* heno waves17:00
pedro_hello everybody!17:00
henobdmurray, ogasawara, sbeattie, schwuk: meeting ping17:01
* ogasawara waves17:01
bdmurrayhi17:01
henoara is on holiday17:01
sbeattiehey17:02
* ogasawara forgot to add some items to the agenda17:03
henoogasawara: go for it17:04
henook, let's start17:04
NCommanderthis is the QA team meeting, right?17:04
sbeattieNCommander: correct17:04
heno#startmeeting17:04
MootBotMeeting started at 11:04. The chair is heno.17:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:04
heno[TOPIC] UDS topics17:04
MootBotNew Topic:  UDS topics17:04
* schwuk waves (with cup of tea in *other* hand)17:04
* NCommander has a request of the QA team once there is a moment to bring up new business17:04
henoI've talked with several of you about UDS topic ideas17:06
henoplease add them to https://blueprints.edge.launchpad.net/sprints/uds-jaunty/+specs17:06
henoshall we agree on a naming convention? qa-* say17:07
davmor2Hi17:07
sbeattieheno: doh. Can they be renamed? :-)17:07
henoI'll flush out https://wiki.ubuntu.com/QATeam/Specs and we'll track them there17:07
henosbeattie: yes, I think so17:08
sbeattiegood. I'm fine with a qa- prefix17:08
heno(perhaps only drivers can do that?)17:08
henosbeattie: ok, page flushed17:09
heno[TOPIC] Alpha 1 testing17:10
MootBotNew Topic:  Alpha 1 testing17:10
henoWe are in alpha 'freeze' now and expect new images tomorrow I guess17:11
henowe need to give them a quick sanity test17:11
henocr3: is your daily build testing machinery running normally now?17:12
james_wlikely to be alternate-only17:12
henodavmor2: can you take a few alternates for a spin tomorrow?17:12
henojames_w: ok, thanks17:13
cr3heno: I haven't touched it in a while and I haven't seen any images on cdimage either yesterday or the day before, I actually checked manually17:13
henowe'll coordinate in #ubuntu-testing as usual17:13
davmor2heno: might be able to when I get back home17:13
cr3heno: there seems to be images though, so I'll see what's going on17:13
henocr3: ok. alpha 1 is always a bit uncertain17:13
cr3heno: ok, best effort then17:14
henoyep17:14
heno[TOPIC] The 2.6.27.3 and 2.6.27.4 kernel stable patch sets17:14
MootBotNew Topic:  The 2.6.27.3 and 2.6.27.4 kernel stable patch sets17:14
henoogasawara: ^17:14
ogasawaraI just wanted to note that those patch sets are in the kernel sitting in intrepid-proposed17:14
ogasawaraif there are any major regressions, let me know17:15
sbeattiewhere's 2.6.27.5 in the process (is it released yet?)17:15
pedro_anything special that'd require more testing?17:15
henocr3 is working on getting some testing for proposed17:15
ogasawarasbeattie: bug 296500 is the SRU for 2.6.27.5 - not released yet or even accepted to -proposed17:15
ubottuLaunchpad bug 296500 in linux "Update to 2.6.27.5 stable kernel" [High,Fix committed] https://launchpad.net/bugs/29650017:15
ogasawarapedro_: I'm happy with boot tests for the most part17:16
cr3ogasawara: when is 2.6.27.6 due?17:16
cr3ogasawara: in other words, should I be testing 2.6.27.5 asap?17:16
ogasawaracr3: 2.6.27.6 is already out - bug 29788517:16
ubottuLaunchpad bug 297885 in linux "Update to 2.6.27.6 stable kernel" [High,Triaged] https://launchpad.net/bugs/29788517:16
ogasawara2.6.27.7 is under review17:16
henoschwuk: he'll add a proposed flag in the submission data base; can you filter on that and make a proposed report?17:16
schwukheno: as long as I can filter out the results we want, sure.17:17
ogasawaracr3: let me rephrase, 2.6.27.6 has been released upstream and we're still in the process of getting it through the SRU process17:17
cr3schwuk: it'll be a bit hacked for now until we find a better way, it's not very clear in my mind yet17:18
henoogasawara: so you recommend that we test with .3 and .4 now and not wait for .5 .6 and .7 to land in proposed?17:18
cr3ogasawara: I mean, when is 2.6.27.6 due in -proposed?17:18
cr3ogasawara: nevermind, heno's question is better17:18
ogasawaracr3: yes, please test .3 and .4 which are in intrepid-proposed right now.  I think the plan is to get those through first before uploading .5, .6, and .717:19
henook, thanks. we'll do that17:20
henoalso, everyone is encouraged to enable proposed!17:20
heno[TOPIC] Jaunty Bug Lists17:20
MootBotNew Topic:  Jaunty Bug Lists17:20
ogasawarawith a focus on fixing bugs for the Jaunty devel cycle, does anyone have any interest in us generating Jaunty bug lists?17:21
ogasawarafor certain packages17:21
sbeattieogasawara: similar to your kernel buglists?17:22
ogasawarawe'd attempted something similar with the Hardy cycle by tagging bugs in launchpad but I'm unsure how successful it went17:22
henoand/or for certain teams?17:22
ogasawarasbeattie: I think maintaining it via launchpad would be better17:22
henoogasawara: this may be a better point in the cycle to do it17:22
henobdmurray suggested using package maintenance in LP as a guide17:23
=== njpatel is now known as njpatel_away
henowe need to find some low-touch way of generating them, that does not involve hand-picking17:24
henoesp in areas we have no core expertise17:25
henousing the regressions list seems good, high subscriber count and comment count17:25
henoshould we generate some lists automatically and then hand-sort from those?17:26
ogasawaraso we really could just advertise use of the status pages since they contain that info?17:26
bdmurrayWe've talked about revisiting ones with a high or critical importance to ensure they are still relevant and looking at missed milestones.17:26
bdmurraynot everything is listed on the status pages though17:27
ogasawarabdmurray: true17:27
henoI think a real list of bug numbers is useful17:27
henowe've talked about using a tag sop it could all be stored in LP17:28
henoqa-jaunty-list ?17:28
bdmurrayMaybe we should see how many bugs there are in each specific area to get an idea of how many bugs we are talking about17:29
ogasawarabdmurray: that would be good.  that could also help measure the progress that gets made17:30
henobdmurray: what do you mean by area in this case?17:30
bdmurraylike 20 critical bugs in Ubuntu, 500 high bugs, 100 bugs that are targetted for later ....17:31
henobdmurray: ok17:32
bdmurraythen we can determine which lists need some refining17:32
henobdmurray: can you collect that and then work with ogasawara to create some preliminary lists?17:33
bdmurrayyes17:33
henofwiw I have another conf call about this on Friday 17.30 UTC17:34
henobdmurray: please join me on that if you're around17:34
henogreat, moving on17:35
henoany other business?17:35
henoNCommander: ^17:35
NCommanderI wanted to ask the QA team on the possibility of released Xfce 4.4.3 via updates to Intrepid and Hardy17:35
NCommander(the current release is 4.4.2 on both)17:36
henoso that would be an SRU - https://wiki.ubuntu.com/StableReleaseUpdates17:36
henowe are not really the gatekeepers for that17:37
cody-somervilleYea17:37
cody-somervilleI decide that17:37
henoand the archive admin / release teams :)17:37
henooh, sorry it's in universe now17:38
henocody-somerville: are you on the motu-sru team?17:38
cody-somervilleYes.17:39
cody-somervilleAnd I'm the Xubuntu project lead.17:39
henoindeed17:40
henoNCommander: so there is your answer :)17:40
NCommanderCody wanted me to run this by the QA team17:40
* NCommander nods17:40
henowe can help give it a test from proposed of course17:41
henoany other other business?17:41
bdmurrayWhat is the difference between 4.4.3 and 4.4.2?  Is it primarily a bug fix release?17:41
james_wI have something I would like to discuss17:41
henojames_w: go ahead17:42
james_wspecifically QA of packages that are in Ubuntu but not in Debian17:43
henobughelper, checkbox, what else?17:43
schwukheno: was just thinking of checkbox :)17:43
henoapport counts I guess17:43
james_wwe have around 800 packages in universe that are not in Debian, and we don't have the QA we get from packages maintained in Debian.17:43
bdmurraypython-launchpad-bugs ;)17:43
henoah, QA _of_ packages17:44
bdmurrayjames_w: is that list available somewhere?17:44
henosorry, misread that17:44
james_whttp://paste.ubuntu.com/74424/17:45
MootBotLINK received:  http://paste.ubuntu.com/74424/17:45
schwukjames_w: is there an effort to get those packages into Debian, or is that what you're wanting to discuss?17:45
james_wthere is not much effort, and that would be one good thing to happen17:45
james_wgetting 800 packages in to Debian is not going to be a quick thing though, so I would like to discuss what to do in the meantime17:46
NCommanderbdmurray, yes, its a bug fix release (there was one new feature added to xfwm4 however)17:46
james_whttp://paste.ubuntu.com/74425/17:47
MootBotLINK received:  http://paste.ubuntu.com/74425/17:47
james_wthat's the number of open bugs per package17:47
james_wand the number of people that subscribe to the bug mail of each package17:47
james_wso there are not that many bugs reported against these packages17:48
henojames_w: what sort of QA is needed in your view? testing, triage, lintian/piuparts?17:48
james_wthat's really my question.17:48
henoa bug day to look into the state of them further perhaps?17:48
james_wWe don't have much visibility in to the quality of these packages, so in the QA team's opinion what would be the most valuable and worthwhile things to do to make sure that we are not shipping bad packages from this set17:49
schwukheno: Isn't 800 a lot for a single day?17:49
sbeattiejames_w: hrm, as a process thing going forward, I wonder if the submitter of the package should be auto-subscribed to that package's bugs, as a "you added it, you get to maintain it"17:49
james_wheno: yes, a bug day for the un-triaged open bugs would be a good idea I think17:49
james_wsbeattie: yes, I would advocate that policy, I don't know if it is possible to do it automatically.17:49
james_wsbeattie: when I sponsor a new package I immediately point the submitter to the package page with a hint that they should subscribe17:50
henoschwuk: looks like less than 800 bugs to me17:51
henothe package with 82 bugs is worth looking at though :)17:52
bdmurrayjames_w: couldn't some of these be removed off the list like python-launchpadlib ...17:52
sbeattiejames_w: something else that may be of interest: correlating the packages with popcon numbers17:52
james_wsbeattie: that would be yes17:53
schwukheno: I was referring to the package count, the bug count is a lot lower :)17:53
james_wbdmurray: well, that one is superbly maintained :-)17:53
bdmurrayI think there are some others like that too.17:53
henoschwuk: right, but we can get a machine to list just the bugs ;)17:54
james_wI'm happy to keep toying with this to see what I can find, and I'll keep you posted on the results.17:54
james_wI think a bug day is a good idea though, so I can help to set it up if it is desired17:54
henojames_w: are you happy to put together a bug day list with help from people here?17:55
bdmurrayjames_w: What action would we take if there is an important bug and no subscribers to the bug reports?17:55
henoassign whoever touched it last :)17:56
james_wbdmurray: good question. Add it to a list of targets I guess, do we have such a thing?17:56
bdmurraythat contradicts the assignment should be taken not given policy17:56
james_wwe could make it RC and then try and encourage more use of RC in universe17:57
henovery true17:57
bdmurrayjames_w: and then if not fixed have package removed?17:57
james_wbdmurray: if the bug is serious enough17:57
henodebian style RC policy, interesting17:57
james_wRC with no milestone if not, so that it is flagged as a "target of opportunity"17:58
henoright, let's start with a bug day on this17:58
henoanything else (in 2 min)?17:59
bdmurrayjames_w: do you mean release targetted with no milestone?17:59
davmor2I need to sod off now.  So I'll try and get some testing in tomorrow night when I get home.  I'll be around all day friday to get some in.  TTYL17:59
james_wI'm also toying with the idea of subscribing ~motu to all the packages, bar a few, so that bugs get sent to the mailing list, but I'm not sure that's a good idea.17:59
james_wbdmurray: yes, sorry.17:59
james_wthanks for your time17:59
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Platform Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Nov 12:00: Ubuntu Mobile Team | 20 Nov 13:00: Desktop Team | 21 Nov 20:00: Tunisian LoCo Team IRC | 25 Nov 16:00: Server Team
heno#endmeeting18:00
MootBotMeeting finished at 12:00.18:00
henothanks everyone!18:00
cr3cheerio18:00
schwukthanks heno18:00
=== ubottu changed the topic of #ubuntu-meeting to: Current meeting: Platform Team Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Nov 12:00: Ubuntu Mobile Team | 20 Nov 13:00: Desktop Team | 21 Nov 20:00: Tunisian LoCo Team IRC | 25 Nov 16:00: Server Team | 25 Nov 17:00: Kernel Team
=== leonel_ is now known as leonel
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 20 Nov 12:00: Ubuntu Mobile Team | 20 Nov 13:00: Desktop Team | 21 Nov 20:00: Tunisian LoCo Team IRC | 25 Nov 16:00: Server Team | 25 Nov 17:00: Kernel Team | 26 Nov 17:00: QA Team

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