/srv/irclogs.ubuntu.com/2012/09/12/#ubuntu-meeting.txt

=== charles__ is now known as Guest11727
=== Guest11727 is now known as charles
=== mmrazik is now known as mmrazik|lunch
=== doko_ is now known as doko
=== mmrazik|lunch is now known as mmrazik
=== Quintasan_ is now known as Quintasan
cyphermox#startmeeting 1200 UTC Ubuntu Membership Board12:03
meetingologyMeeting started Wed Sep 12 12:03:18 2012 UTC.  The chair is cyphermox. Information about MeetBot at http://wiki.ubuntu.com/meetingology.12:03
meetingologyAvailable commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired12:03
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | 1200 UTC Ubuntu Membership Board Meeting | Current topic:
cyphermoxHello and welcome to the Ubuntu Membership Review Board for the 1200 UTC meeting for September 12, 2012.12:03
cyphermoxThe wiki page for the Review Board is available here: https://wiki.ubuntu.com/Membership/Boards12:03
cyphermoxWe will attempt to get through all of the applicants that have added themselves to that list before today's meeting. If we are unable to make it through the entire list due to time constraints, then at the next meeting we will pick up where we left off.12:03
cyphermoxThe format for the meeting is as follows: We will go through the list of applicants one by one, by date of application (FIFO).12:04
cyphermoxEach applicant should introduce themselves (1-5 sentences) and provide links to their Ubuntu Wiki page. After the introduction the members of the Membership Review Board will review the pages and, if needed, ask the applicant further questions.12:04
cyphermoxDuring this time it is encouraged for other members of the community to show their support for the applicant. Do not be alarmed if the members of the Membership Review Board are quiet during this time; they are most likely reading wiki/launchpad/forum/other pages and deciding how they are going to vote.12:04
cyphermoxWhen the board is ready to vote, they will publicly vote in the channel with either +1, 0, or -1 (for membership, abstain, and against membership, respectively). If the sum of those numbers is positive, then the applicant is now an official Ubuntu member! (feel free congratulate them!)12:04
cyphermox#voters cyphermox Pendulum head_victim hggdh12:04
meetingologyCurrent voters: Pendulum cyphermox head_victim hggdh12:04
head_victimLet's hope we can get through the long list of applicants tonight ;)12:04
cyphermoxomg!12:04
untaintableangellol12:04
cyphermoxNow, with any further ado, lets get started with the first applicant...12:05
cyphermox#subtopic Anthony Harrington12:05
untaintableangelHello, everyone! My Name's Anthony and here's a link to my launchpad page: https://launchpad.net/~untaintableangel12:05
untaintableangelalso to my wiki: https://wiki.ubuntu.com/AnthonyHarrington12:05
cyphermox#link https://launchpad.net/~untaintableangel12:05
cyphermox#link http://wiki.ubuntu.com/AnthonyHarrington12:06
cyphermox(belt and suspenders, just making sure it's there in the meeting report thingy)12:06
untaintableangelI'm 22, i study chemistry at university and i'm from the northeast of england. I'd like to become an official ubuntu member :D12:06
cyphermox#voters cyphermox Pendulum head_victim hggdh micahg12:07
meetingologyCurrent voters: Pendulum cyphermox head_victim hggdh micahg12:07
head_victimuntaintableangel: after reading your application and looking over the links, I'm curious about something. Not to belittle your translation efforts (nice karma for that!) are you involved in any other aspects of the community?12:09
untaintableangelNot currently, but in time i hope to provide coding related contributions and helping users answer questions in the ubuntuforums12:10
Pendulumuntaintableangel: Have you had any involvement with the UK LoCo as far as events or interacting with members online other than translations?12:10
untaintableangelAgain, not currently, emails sent between me and other launchpad members are predominantly concerning translations12:11
cyphermoxuntaintableangel: have you had contact with other Ubuntu members in your translation work?12:11
cyphermoxWhy would you like to be a Ubuntu member?12:13
cyphermoxuntaintableangel: still around?12:16
ant__oh dear, i think my last message didn't go through, i'll type it again12:17
cyphermoxlast I saw was "<untaintableangel> Again, not currently, emails sent between me and other launchpad members are predominantly concerning translations"12:18
hggdhlet's give him a chance of either (1) finishing his typing, or (2) reconnecting12:19
ant__I was saying, time does become very scarce during university term time and especially around exams so i do unfortunately miss out on events, and i have to contribute where at all possible time-wise.12:20
ant__<untaintableangel> Yes, i get quite a few emails from users seeking advice or requesting assistance to complete a set. Every now and then i make sure to circulate several messages of encouragement to the team/users to spur them on in their efforts :)12:20
head_victimant__: is that on mailing lists of offlist?12:20
hggdhoh, anr__ == untaintableangle12:20
ant__both12:21
hggdhs/anr__/ant__12:21
head_victimI just hadn't seen much on the engb list in a long time (I'm a subscriber, I translate enAU)12:21
ant__yes, sorry lol i don't know why my idendity changed and i don't know how to change it back XD12:21
=== ant__ is now known as untaintableangel
untaintableangelthere we go, that's better lol12:21
untaintableangelahhh, hi there12:22
head_victim:)12:22
cyphermoxah, I looked at the engb list too, but just the last few months12:22
cyphermoxuntaintableangel:  Why would you like to be a Ubuntu member?12:23
untaintableangelI'd love to become an official ubuntu member because i've dedicated many years towards its translations and it has become such a great part of my life that i'd like to 'officially' be 'more intertwined' with it, if you will. lol12:24
untaintableangelWhat i'm saying is: ubuntu is something to be proud of and i'd like to be officially associated with it12:25
hggdhuntaintableangel: what we are trying to ascertain is how involved with the community-at-large you are12:27
hggdhso please give us data on that12:27
untaintableangeli see, well i'm known to other english translators, certainly, and well known to specific teams like emesene12:28
untaintableangelbut really, not much outside of launchpad12:29
untaintableangel'at the moment' being the key point though. I would certainly be more involved at-large if i could contribute coding related things but i don't have the expertise just yet, i'm afraid :(12:30
cyphermoxit doesn't have to be coding12:32
Pendulumuntaintableangel: there is more "community at large" than just coding (I've never done any translations and I'd been a member for over a year before I did any code)12:32
cyphermoxLet's get to the voting part12:32
cyphermox#vote Anthony Harrington to obtain Ubuntu Membership12:32
meetingologyPlease vote on: Anthony Harrington to obtain Ubuntu Membership12:32
meetingologyPublic votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)12:32
hggdh+1 I would really like to see more community-at-large involvement, but the translation work justifies it (albeit minimally)12:33
meetingology+1 I would really like to see more community-at-large involvement, but the translation work justifies it (albeit minimally) received from hggdh12:33
cyphermox+1 , please get more involved with other parts of the community where possible (like your LoCo team); you could be a great motivator for others to do translation work12:33
meetingology+1 , please get more involved with other parts of the community where possible (like your LoCo team); you could be a great motivator for others to do translation work received from cyphermox12:33
head_victim+1 A suggestion I have moving forward would be to try to interact more with the community in whatever area you like but your efforts to date warrant membership as is12:34
meetingology+1 A suggestion I have moving forward would be to try to interact more with the community in whatever area you like but your efforts to date warrant membership as is received from head_victim12:34
Pendulum+1 good work with translations, but I'd love to see more community interaction (LoCo, maybe translations jams, etc.)12:34
meetingology+1 good work with translations, but I'd love to see more community interaction (LoCo, maybe translations jams, etc.) received from Pendulum12:34
untaintableangelI promise, i won't let you down :)12:34
head_victimuntaintableangel: an example of how to get involved without having to code would be to run a translation jam with your loco or something similar :)12:34
cyphermoxyeah! that's a great idea12:34
untaintableangela translation jam?12:35
micahg+0 excellent translations work, but would have liked to see more integration with existing members12:35
meetingology+0 excellent translations work, but would have liked to see more integration with existing members received from micahg12:35
cyphermoxespecially explaining at least the use and context in translating to en_GB12:35
head_victimuntaintableangel: https://wiki.ubuntu.com/UbuntuGlobalJam12:35
Pendulumuntaintableangel: also, if you use IRC at all, hang out in the #ubuntu-uk IRC channel and that may give you some ideas on what's going on that you could do without too much more time on your part12:35
cyphermox#endvote12:36
meetingologyVoting ended on: Anthony Harrington to obtain Ubuntu Membership12:36
meetingologyVotes for:4 Votes against:0 Abstentions:112:36
meetingologyMotion carried12:36
head_victimI'm sure the lovely folk in #ubuntu-uk would be a good place to start :)12:36
=== Quintasan_ is now known as Quintasan
cyphermoxCongratulations untaintableangel12:36
untaintableangel:D Thank you!!!12:36
head_victimCongratulations untaintableangel, keep up the good work :)12:36
untaintableangelwooooooo12:36
hggdhuntaintableangel: welcome. Please do get around to know your community ;-)12:37
cyphermoxIf you have a blog, don't forget you should be able to add it to planet.ubuntu.com shortly :)12:37
untaintableangelThank you so much everyone :) I will become more involved12:37
cyphermox(pending I do the necessary magic)12:37
hggdhblogging, yes, good point12:37
hggdhbah, cyphermox IS a magic12:37
cyphermoxpff12:37
untaintableangellol12:37
cyphermoxAny other business?12:37
Pendulumuntaintableangel: congrats!12:38
hggdhno, I think we are done, cyphermox12:38
cyphermoxgood good12:38
cyphermox#endmeeting12:38
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Sep 12 12:38:25 2012 UTC.12:38
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-12-12.03.moin.txt12:38
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-12-12.03.html12:38
untaintableangel:)12:38
cyphermoxyay, the "#link" were useful. I knew it!12:39
hggdhuntaintableangel: the whole point is that a community is made by the people you directly interact with, the ones that depend on  your work, and the "others". Getting to know as many as you can outside your expertise area glues much better the community12:40
untaintableangelThank you for your time and words of wisdom, everyone. Have a good day! :)12:42
hggdhuntaintableangel: a good night for you, sir12:43
=== sagaci_ is now known as sagaci
=== cjohnston_ is now known as cjohnston
balloonsgood morning/evening14:00
smartboyhwGood evening here14:01
smartboyhwphillw: Say good morning/14:01
balloons#startmeeting Ubuntu QA Community14:01
meetingologyMeeting started Wed Sep 12 14:01:22 2012 UTC.  The chair is balloons. Information about MeetBot at http://wiki.ubuntu.com/meetingology.14:01
meetingologyAvailable commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired14:01
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Community Meeting | Current topic:
phillwgood afternoon from UK14:01
balloonswho all is here?14:02
kanlioto/14:02
smartboyhw\o14:02
phillwo/14:02
balloons:-) so quick nice14:02
balloonslet's dive in shall we.14:02
smartboyhw;-)14:02
balloons[TOPIC] Previous Actions14:03
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Community Meeting | Current topic: Previous Actions
balloonsI believe the only outstanding item is me to get the https://qa.ubuntu.com/ site fixed14:03
smartboyhwlol 3 weeks issue now:)14:03
balloonsthe ticket is still outstanding.. I'm still waiting :-(14:03
balloonsit's going to take time14:03
phillwjust have to keep reminding them :)14:04
balloonsyep14:04
smartboyhw:)14:04
balloonsok, so moving along then14:04
balloons[ACTION] balloons to follow-up with ubuntu-qa website changes14:05
meetingologyACTION: balloons to follow-up with ubuntu-qa website changes14:05
balloons[TOPIC] Ubuntu Updates14:05
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Community Meeting | Current topic: Ubuntu Updates
balloonsSo updates for ubuntu :-) Well knome has been working on visually enhancing our testcases14:05
balloonshttps://bugs.launchpad.net/ubuntu-qa-website/+bug/103915814:05
ubottuLaunchpad bug 1039158 in Ubuntu QA Website "Add css to have dl/dt/dd show as numbered list for testcases" [Wishlist,Fix committed]14:05
smartboyhwYes and I destroyed it:)(14:06
smartboyhwBy not knowing it:(14:06
smartboyhwSorry everybody:)14:06
balloonsAnd I've been working on writing the new testcases for ubiquity and migrating the alt cases over as needed14:06
* smartboyhw goes and looks at the sandbox14:07
balloonsIn addition, focus is being given now to getting the flavors on board with re-using the ubuntu testcases and adding flavor specifics in there own testcases14:07
kanlioti sent phillw some testcases, i wonder if he saw em.  They were from the fedora team14:07
phillwkanliot: yes, I have them & the ideas from Julien to look throughj.14:07
balloonsSo, in addition, beta is behind us, ff is behind us.. things are starting to stabilize a bit14:10
smartboyhwYay!14:10
* balloons checking schedule14:11
balloonsSept 27th is beta214:11
phillwindeed, 2 weeks.14:11
balloonsonce that hits it will be quite an october full of testing14:11
balloons:-)14:12
smartboyhw;014:12
balloonsI think that's it for updates themselves.. any questions before we move on?14:12
smartboyhwNo.:)14:13
balloons[TOPIC] Other topics14:14
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology | Ubuntu QA Community Meeting | Current topic: Other topics
balloonsthat means the floor is open14:15
phillwo/14:15
kanliothttps://bugs.launchpad.net/bugs/104656314:17
ubottuLaunchpad bug 1046563 in update-manager (Ubuntu) "update-manager never appears on lubuntu precise" [Undecided,Confirmed]14:17
kanliotcould use some help communicating with the maintainer14:18
smartboyhwkanliot: Please \o14:18
smartboyhwand wait for the chair (balloons' approval) before you speak:)14:18
balloonsgo ahead phillw14:18
kanliotam i outta order?14:18
smartboyhwkanliot: You are:)14:18
balloonskanliot, yes, but no worries14:18
phillwthe x-bug affecting ppc appears to have been a red herring as that fix was for graphic chips that ppc computers do not have.14:19
phillwwork is ongoing to add a command similar to the nomdeset command.14:20
phillwit does not seem, at this time, that the bug is reproducable in a Virtual Machine, so it is heavily reliant on the L-QA guys who have the hardware.14:21
phillw..14:21
smartboyhw\o14:22
balloonsthanks phillw .. that's good news14:22
balloonskanliot, go ahead14:22
kanliotok bug https://bugs.launchpad.net/bugs/104656314:22
ubottuLaunchpad bug 1046563 in update-manager (Ubuntu) "update-manager never appears on lubuntu precise" [Undecided,Confirmed]14:22
kanliotneed help communicating with the maintainer14:22
kanliotto help suggest solutions14:22
smartboyhwThat's awkward weird14:23
kanliotpretty much update manager turned it'self off on lubuntu last month\14:23
balloonskanliot, really? phillw hear of others having the same issue?14:24
balloonsthat's really bizarre14:24
kanliotyeah i'm surprised that more people arent upset14:25
balloonsbasically, there's updates, but you'll never be prompted14:25
kanliotbut i get upset about everything, so it's normal for me14:25
balloonsdid you check and make sure the settings to prompt are correct?14:25
phillwballoons: I'd have to fire up a VM, but it is confirmed by another tester14:25
balloonsperhaps reset them?14:25
balloonsphillw, ahh.. yes, we're all in quantal mode14:25
smartboyhwMe too I'm in quantal mode (and no Lubuntu ONLY)14:25
phillwballoons: I'll dig out from my other drive an 12.04 lubuntu and run the upgrades through it on a VM - but my internet speed is slow, so it will take quite a few hours :(14:27
smartboyhwDon't worry we do have time:)14:27
balloonsphillw, no no.. I can confirm it much quicker than that14:27
kanliotit's pretty clearly broken14:27
smartboyhwballoons: :)14:27
balloonsbut the point is it's been confirmed14:27
kanliotyou can run the update manager through the cron script when it's working14:27
balloonsso I'm not worried about that.. just wanted to see how much debugging has been done14:27
kanliotand when it's broken, the cron script doesn nothing14:27
kanliotso reproducing isn't the problem14:28
balloonsok kanliot i'll bring this up and see if we can get someone to give feedback on it14:28
balloonsthanks14:28
kanliotthe problem is that all lubuntu people wont get updates if they upgrade to 12.0414:28
kanliotty balloons14:28
balloonsyw14:28
smartboyhw\o14:28
balloonssmartboyhw, go ahead14:28
smartboyhwballoons: Just a small one14:28
balloonssure14:28
smartboyhwand a reminder only:)14:28
smartboyhwhttps://wiki.ubuntu.com/QATeam/Meetings/QA/2012090514:28
smartboyhwyou forgotten to add it to https://wiki.ubuntu.com/QATeam/Meetings14:29
smartboyhw:)14:29
smartboyhw..14:29
phillwsmartboyhw: it is there, just waiting on balloons to fix the regex :P14:29
* balloons is booting lubuntu 12.04 to see what happens14:29
smartboyhw;P14:29
balloonsphillw, ohh right.. that regex.. my changes must not have saved14:29
balloonsperhaps I never saved it14:29
balloonslol14:29
phillwhe he.14:30
balloons[ACTION] balloons to fix regex on https://wiki.ubuntu.com/QATeam/Meetings14:30
meetingologyACTION: balloons to fix regex on https://wiki.ubuntu.com/QATeam/Meetings14:30
smartboyhwlol14:30
smartboyhw..14:30
balloonsok, any other questions?14:31
smartboyhwNo. End the meeting:)14:32
balloonsphillw, kanliot testing the update-manager bug right now14:33
balloons#endmeeting14:33
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Sep 12 14:33:05 2012 UTC.14:33
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-12-14.01.moin.txt14:33
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-12-14.01.html14:33
smartboyhwTHanks balloons14:33
balloonslet's chat in #ubuntu-testing14:33
smartboyhwAnd phillw and kanliot14:33
phillwthanks for chairing balloons14:33
* smartboyhw runs to #ubuntu-testing14:33
cjwatsonHi folks15:00
stokachuo/15:00
infinityo/15:00
stokachu\o15:00
jodh\o/15:00
* xnox \0/15:00
stokachu/o/15:00
ogra_*plop*15:00
jodhwe need to practise the YMCA y'all.15:00
stokachulol15:00
cjwatsonSteve is in a hot tub drinking champagne^W^W^W^W^W^Wat a managers' sprint, so asked me to run the meeting15:01
cjwatson#startmeeting15:01
meetingologyMeeting started Wed Sep 12 15:01:18 2012 UTC.  The chair is cjwatson. Information about MeetBot at http://wiki.ubuntu.com/meetingology.15:01
meetingologyAvailable commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired15:01
cjwatson#topic lightning round15:01
=== meetingology changed the topic of #ubuntu-meeting to: lightning round
cjwatson$ echo $(shuf -e barry bdmurray cjwatson ev doko ogra jodh stgraber infinity xnox stokachu)15:01
cjwatsonstokachu jodh xnox barry cjwatson ogra stgraber doko ev infinity bdmurray15:01
* infinity naps.15:01
stokachu- working on bug regression for libgcrypt, swamped in customer issues, backporting multi-arch into precise for the ones that have been approved, testing/verifying approved multiarch srus15:03
stokachudone15:03
evoh yes, team meeting15:03
* ev scrambles15:03
jodh* blueprints15:03
jodh  - foundations-q-session-management:15:03
jodh    - no progress.15:03
jodh  - desktop-q-upstart-session-requirements15:03
jodh    - not started.15:03
jodh  - foundations-q-upstart-service-readiness15:03
jodh    - no progress.15:03
jodh  - foundations-q-upstart-roadmap15:03
jodh    - no progress.15:03
jodh  - foundations-q-event-based-initramfs:15:03
jodh    - reviewing slangaseks changes.15:03
jodh    - collaboration with cjwaton on ptrace parent semantics:15:03
jodh      - wading through kernel code and writing tests both confirm that15:03
jodh        if a "debugger" re-execs, it retains its debugger status over15:03
jodh        ptraced children. This behaviour appears not to be documented.15:03
jodh    - allow unflushed log data to include null bytes in serialised data.15:03
jodh    - fixed issue where 2nd and subsequent re-exec stopped log data serialisation.15:03
jodh    - reviewed and merged lp:~jconti/upstart/fix_empty_chroot.15:04
jodh    - reviewed lp:~cjwatson/upstart/stateful-reexec-ptrace.15:04
jodh    - started writing tests (for sessions). This has uncovered an issue15:04
jodh      with how empty strings are encoded which has necessitated a lot of15:04
jodh      macro tweaks (in progress).15:04
jodh* upstart15:04
jodh  - bug 1049820: informed user of workaround and identified fix.15:04
ubottuLaunchpad bug 1049820 in upstart "Using kill signal SIGPWR results in system crash" [Medium,Confirmed] https://launchpad.net/bugs/104982015:04
jodh~15:04
jodhsorry ev - I'm not getting competitive, honest!15:04
slangasekjodh: any further comments on my merge request?  is it time to merge it?: )15:04
jodhslangasek: which one? :) Do you mean the partial handling one?15:04
evhahaha15:05
slangasekjodh: yes15:05
cjwatsonthanks for the comments on my MP; I'll get to them once I'm out from under a few other things15:05
jodhwell, the session test I'm currently working on touches on that whole area. TBH, I think that if we drop the partial handling, we also need the redesign whereby we serialise in the parent since we its a lot messier to back-out of an event_new() than creating a partial event.15:06
cjwatsonI thought the agreement was that serialising in the parent was simpler anyway ...15:06
jodhslangasek: so, I think we do need to simplify that whole area, but it requires other changes to be applied together so I'll work on that.15:06
xnox* rls-q-tracking:15:07
xnox - btrfs-tools mark quantal task as fixed released, due to merging new15:07
xnox   upstream release back in may. Precise task is still open.15:07
xnox - partman-auto-lvm fixed 154086 in precise & quantal, patch send to15:07
xnox   debian as well (stokachu *wink* )15:07
xnox - autofs bug #488696 did some analysis options are to fix buggy15:07
xnox   lex/bison parser or to rewrite it in C (as libc does). But I don't15:07
ubottuLaunchpad bug 488696 in autofs5 (Ubuntu Precise) "syntax error in nsswitch config near [ syntax error ]" [High,Triaged] https://launchpad.net/bugs/48869615:07
xnox   have working lex/bison knowledge nor want to spend time ripping15:07
xnox   libc specific bits out of the libc parser. Anyone up for fun times15:07
xnox   with lex/yacc?!15:07
xnox - proposed a branch to fix the top crashes in ubiquity bug #1027648,15:07
ubottuLaunchpad bug 1027648 in ubiquity (Ubuntu Quantal) "ubiquity crashed with ValueError in command(): I/O operation on closed file." [High,Confirmed] https://launchpad.net/bugs/102764815:07
xnox   which is actually yet another incarnation of an older bug #792652.15:07
xnox   Please review https://code.launchpad.net/~xnox/ubiquity/fix-value-errors/+merge/12372715:07
ubottuLaunchpad bug 792652 in ubiquity (Ubuntu Precise) "ubiquity crashed with ValueError in command(): I/O operation on closed file" [High,Fix released] https://launchpad.net/bugs/79265215:07
xnox* ubiquity:15:07
xnox - many bugfixes committed and uploaded15:07
jodhyes it is and we plan to do that, but I'm currently working on the tests, being higher priority than that parent-serialisation work (it's in the TODO list :)15:07
xnox - good progress on hooking up manual crypt UI15:07
xnox - spent some time chatting with Riddell, Qt Automatic LVM & LUKS has15:07
xnox   landed in trunk, pending FFe bug 104871215:07
ubottuLaunchpad bug 1048712 in ubiquity (Ubuntu Quantal) "FFe [kde] add LVM and LUKS options" [High,Confirmed] https://launchpad.net/bugs/104871215:07
cjwatsonfix-value-errors> on my list (somewhere), thanks15:07
* xnox realised it's my turn.15:07
cjwatsonneed to think hard about that15:07
xnoxtrue....15:08
xnox.. *done* ..15:08
barrymore consumption of gwibber spaghetti, but it's getting progressively more gluten-free as we're nearing completion of the py3 port.  worked a bit on support for the py3 port of twisted (buildbots, ppas).  bug #1048710 (patches landed upstream, but discussion is ongoing).  bug #887699 (postponed).  no change to q blueprints.  will atone today for my lack of patch piloting yesterday.  will continue with r planning of py3 work.  done.15:09
ubottuLaunchpad bug 1048710 in python3.2 (Ubuntu) "Regression in argparse for Python 2.7, 3.2 and 3.3" [Critical,Confirmed] https://launchpad.net/bugs/104871015:09
ubottuLaunchpad bug 887699 in python-distutils-extra (Ubuntu) "python-mkdebian: Support python3 projects" [High,Triaged] https://launchpad.net/bugs/88769915:09
slangasekjodh: hmm, I don't agree that these things are tied; I think the 'partial' reworking stands on its own...  but ok, we can discuss outside the meeting15:10
cjwatsonGot permission to open-source the bits of cdimage that weren't already released, in conjunction with my Python rewrite; so I've been powering ahead with that rewrite.  In branch hell at the moment.15:10
cjwatsonWorking on GRUB 2.00 packaging; FFe approved as long as I get it landed this week, so aiming for that.  Testing looking fairly good so far.15:11
cjwatsonWorked on a test for ptrace handling across stateful-reexec in Upstart.  Needs a few tidy-ups before landing, but James and I confirmed that ptrace is preserved which saves a chunk of work.15:11
cjwatsonTidied up various glitches in the squashfs-base server image (bug 1028453, bug 1049011).15:11
ubottuLaunchpad bug 1028453 in livecd-rootfs (Ubuntu) "Quantal Ubuntu Server minimal install oversized" [High,Fix released] https://launchpad.net/bugs/102845315:11
cjwatsonAdded a couple of binaries to ubuntustudio-meta on request of the Ubuntu Studio folks.15:11
ubottuLaunchpad bug 1049011 in live-installer (Ubuntu Quantal) "Quantal server installation fails to install kernel" [Critical,Fix released] https://launchpad.net/bugs/104901115:11
cjwatsonBackported fix for data-loss bug in 'sort -u' (bug 1038468).15:11
ubottuLaunchpad bug 1038468 in coreutils (Ubuntu Precise) "data loss on sort -u" [High,In progress] https://launchpad.net/bugs/103846815:11
cjwatsonLots of rebuilds for glew and tiff transitions.15:11
cjwatson..15:11
ogra_done:15:11
ogra_ * plenty of ac100 testing, fixing etc15:11
ogra_ * held panda install hangout talk http://www.youtube.com/watch?v=jsIW7EF103A15:11
ogra_ * flash-kernel: worked on hiding boot devices15:11
ogra_ * started on updating the arm install wikis15:11
ogra_ * some GLES driver work (kernel tests etc for fixing the remaining issues) for bug 104549115:11
ubottuLaunchpad bug 1045491 in pvr-omap4 (Ubuntu Quantal) "Moving mouse messes up the desktop" [High,Confirmed] https://launchpad.net/bugs/104549115:11
ogra_ * looked into lshw, it defaults to run dmidecode as first test on all arches, started looking into a fix15:11
ogra_todo:15:11
ogra_ * finish flash-kernel changes15:11
ogra_ * inspect framebuffer and kbd issues with d-i on panda (1045855 and 1045788)15:11
ogra_ * get the kernel fixes for 1045491 finally applied15:11
ogra_ * finish wikipages15:11
ogra_..15:11
stgraber - Container15:12
stgraber   - Worked on upstream repository, got daily builds setup, soon to be integrated with the test suite (Serge is working on that part)15:12
stgraber   - Announced the upstream staging branch, reviewed and merged quite a few more changes15:12
stgraber   - Rewrote lxc-start-ephemeral in python3 using the API (used to be shell) and pushed upstream15:12
stgraber   - Reviewed Serge's changes to the server guide (covering apparmor changes, seccomp, hooks and API)15:12
stgraber   - Started preparing a blog post on the API15:12
stgraber - Release15:12
stgraber   - Beta-1 release with the usual tweaks to lp:ubuntu-archive-tools15:12
stgraber   - A few FFe/UIFe reviews15:12
stgraber - Networking15:12
stgraber   - Spent some time going through bug 1003656 again, hopefully fixed for good this time. Forwarded change to Debian.15:12
ubottuLaunchpad bug 1003656 in bridge-utils (Ubuntu Precise) "bridge-utils/vlan udev hooks prevent execution of upstart hook, slowing down boot" [Low,Triaged] https://launchpad.net/bugs/100365615:12
stgraber   - Re-added missing dhclient-script code checking for /etc/resolv.conf writability (when not using resolvconf), forwarded to Debian15:12
stgraber   - Uploaded resolvconf with bugfix for bug 1035076 and bug 99457515:13
ubottuLaunchpad bug 1035076 in resolvconf (Ubuntu) "dnscache resolvconf update script still accesses /etc/resolvconf/run/" [High,Fix released] https://launchpad.net/bugs/103507615:13
stgraber   - Reviewed fix in bug 752481 and uploaded15:13
ubottuLaunchpad bug 994575 in resolvconf (Ubuntu Precise) "/etc/ppp/ip-up.d/000resolvconf should "exit 0" if pppd was run by NM, since NM will register the nameserver addresses itself" [Undecided,Fix committed] https://launchpad.net/bugs/99457515:13
ubottuLaunchpad bug 752481 in ifupdown (Ubuntu) "networking is not actually brought down/up when moving to/from runlevel 1" [Medium,Fix released] https://launchpad.net/bugs/75248115:13
stgraber - Other15:13
stgraber   - Some ARB package reviews15:13
stgraber   - Tested new grub2 from cjwatson's PPA15:13
stgraber - TODO15:13
stgraber   - Continue with isc-dhcp bugfixes15:13
stgraber   - Look at merging ifupdown 0.7.2 (should be bugfix only)15:13
stgraber   - Go through the other networking related packages seeing if there's something else that needs fixing for 12.1015:13
stgraber   - ISO tracker work15:13
stgraber(DONE)15:13
cjwatsondoko: ?15:15
doko- openjdk-7 backport for precise15:15
doko- binutils and gcc-4.7 updates (toward the 2.23 and 4.7.2 releases).15:15
doko- start ubuntu+1 maintenance15:15
doko- worked on component mismatches, filed outstanding bug reports, pestered people, and processed some MIRs15:15
doko- cleaning up NBS, bug fixes, package removals15:15
doko(done)15:15
ev- Massive http://errors.ubuntu.com deployment.15:15
ev  - We've now gone live with our own handling of openid. Your session will be15:15
ev    cached - you'll no longer have to log into every individual problem or15:15
ev    instance page. This also will let us map your teams to the packages those15:15
ev    teams are responsible for, in order to give you a custom view of the most15:15
ev    common problems table.15:15
ev  - We've iterated over the most common problems table a lot. The coloring15:16
ev    should be a bit more obvious (we're still working through this) and it15:16
ev    should be a lot easier to read overall.15:16
ev  - The graph finally has a denominator of the number of unique systems over a15:16
ev    90 day span. I have to manually run a script for each day for this until15:16
ev    my merge to canonical-memento gets merged.15:16
ev  - The graph now changes to reflect what packages and Ubuntu version you've15:16
ev    selected. So you can now see how often software-center crashes over time.15:16
ev  - You can create bug links where they don't already exist. Woo.15:16
ev  - The Loading of the most common problems table has been sped up again. In15:16
ev    my tests it loads somewhere between 1483 and 1988ms, but production is15:16
ev    still somehow a bit sluggish. Investigating further.15:16
ev  - The coloring of the most common problems table actually reflects the15:16
ev    selected release. The first seen and last seen fields do as well.15:16
ev- Started testing Cassandra authentication on behalf of the webops team so15:16
ev  that we can give Brian read-only access to the DB.15:16
ev- Lots of bug fixes. I'll spare you listing them all here for a change.15:16
ev- Merges from both Brian and Matthew. Yay contributors!15:16
ev(done)15:16
infinity- kernel SRU wrangling15:16
infinity- utouch->oif rename SRU reviews/shepherding15:16
infinity- other random SRU and AA work15:16
infinity- some FFe reviews15:16
infinity- discussions about offspring and cdimage mating15:16
infinity- discussions with IS about the state of buildd upgrades15:16
infinity- worked on livefs-in-soyuz stuff a bit15:16
infinity- a few FTBFS fixes15:16
infinity- looked into dpkg SRU for bug #62487715:16
infinity- started looking at clang updates15:16
infinity………15:16
ubottuLaunchpad bug 624877 in linux (Ubuntu) "INFO: task dpkg:23317 blocked for more than 120 seconds." [Undecided,Confirmed] https://launchpad.net/bugs/62487715:16
evsorry if that's entirely incoherent. I was working with Matthew on how we present the coloring if we're showing all the releases at once, and entirely forgot we had the meeting. Oops.15:17
bdmurrayresearch into package install failures and less useful dpkgterminallog files - 'can not write log'15:17
bdmurrayadded patch / branch information to rls-q-tracking and incoming reports15:17
bdmurrayadded count per team to rls-q reports on cranberry15:17
bdmurrayerrors branch to display Launchpad bug report on a bucket page15:17
bdmurrayerrors branch to sort package versions on a bucket page15:17
bdmurrayerrors branch to display the release(s) a package version is in on a bucket page15:17
bdmurraymodified needs-packaging wishlisting code to be more lenient regarding bug title renaming15:17
bdmurraybranch for sponsoring page to show nominated tasks (bug 833706)15:17
ubottuLaunchpad bug 833706 in ubuntu-sponsoring "Show pending SRU nominations" [Undecided,Fix released] https://launchpad.net/bugs/83370615:17
bdmurraybug fix for aptdaemon bug 87587915:17
bdmurrayworked on fixing apport bug 103922015:17
ubottuLaunchpad bug 875879 in aptdaemon (Ubuntu Precise) "update-manager crashed with AttributeError in show_diff(): 'NoneType' object has no attribute 'group'" [High,Triaged] https://launchpad.net/bugs/87587915:17
ubottuLaunchpad bug 1039220 in apport (Ubuntu Quantal) "don't report crashes for programs that don't match the file on disk (like for kernel crashes)" [High,In progress] https://launchpad.net/bugs/103922015:17
bdmurraydone15:18
cjwatsonok, thanks all15:20
cjwatson#topic bugs15:20
=== meetingology changed the topic of #ubuntu-meeting to: bugs
cjwatsonmy rough impression is that rls-q-tracking has been trending downwards, but I don't know if there are any graphs of that so I'm going off memory15:20
bdmurrayI ran across bug 988583 again and was wondering if that might be fixed with the new version of grub215:20
ubottuLaunchpad bug 988583 in grub2 (Ubuntu) "grub-mount hangs when update-grub is ran" [High,Triaged] https://launchpad.net/bugs/98858315:20
bdmurraycjwatson: there are no graphs for rls-q-tracking but there is a number in the report now15:21
cjwatsonbdmurray: it's certainly possible; there've been a number of changes in the hfsplus driver15:21
bdmurrayand I recall it being at around 50 last week15:21
evoooh, is one of those changes write support?15:22
cjwatsonincluding things like "Add btree loop check"15:22
cjwatsonev: ... in grub?15:22
evhahaha15:22
evsorry15:22
bdmurrayadditionally per steve's suggestion I added in a P and a B for bugs with patches or branches15:22
evI missed that part :)15:22
cjwatsonknee.  stop jerking.15:22
cjwatsonbdmurray: I'll leave a note on that bug asking for testing15:23
bdmurraycjwatson: okay, thanks15:23
bdmurraywith the dropping of the alternates cdromupgrade will no longer be supported - is that correct? bug 104520115:24
ubottuLaunchpad bug 1045201 in update-manager (Ubuntu) "Precise to Quantal: cdromupgrade of Ubuntu Desktop failed with cannot calculate dependencies" [Medium,Triaged] https://launchpad.net/bugs/104520115:24
cjwatsonwe should probably go round images and check, but that's my understanding15:24
xnoxi wonder though... there is a package pool on the quantal cd's with optional/restricted packages....15:25
xnoxdoes update-manager pick that up as upgrade pool?15:25
cjwatsonit's probably still on the server CD, probably mistakenly15:25
cjwatsonsince apt isn't going to have a whole lot of luck upgrading the base system from the squashfs15:26
cjwatsonxnox: you know I'm actually not sure15:27
bdmurrayso it sounds like there is some testing to be done15:28
cjwatsonupdate-notifier distinguishes between "CD with packages", "CD with dist-upgrader", "CD with addons", "CD with aptoncd"15:28
* xnox commented on the bug15:29
cjwatsonI don't think we'll get the dist-upgrader one but it might well show up as having packages15:29
cjwatsonarguably correctly15:29
cjwatsonThis is the difference between:15:29
cjwatson  A volume with software packages has been detected.  Would you like to open it with the package manager?15:29
cjwatsonand:15:29
cjwatson  A distribution volume with software packages has been detected.  Would you like to try to upgrade from it automatically?15:30
xnoxcjwatson: will you comment on the bug?15:32
* xnox didn't even think about aptoncd15:33
cjwatsonit's actually not relevant because it's commented out15:33
xnoxalso how does one produce "DVD with dist-upgrader" for personal reasons.15:33
cjwatsonpackages vs. dist-upgrader are the only two we actually need to care about15:33
cjwatsonI suggest you start with data/apt-cdrom-check in update-notifier15:33
cjwatsonanyway all the stuff that apt-cdrom-check looks for is basically under the same chunk of code in debian-cd15:34
cjwatsonso it's easy enough to switch on and off15:34
cjwatson(for dist-upgrader support)15:34
cjwatsonI've commented on the bug by the time-honoured method of copy and paste15:35
cjwatsonnext?15:35
* xnox who is "you" in the "I suggest you.."? (or did my connection drop and I missed something)15:35
cjwatsonxnox: you, since you asked 'how does one produce "DVD with dist-upgrader"'15:35
xnoxah ok.15:35
bdmurrayis bug 1013681 still something fixable for quantal?15:35
ubottuLaunchpad bug 1013681 in apt (Ubuntu Quantal) "make apt-key net-update secure" [High,Triaged] https://launchpad.net/bugs/101368115:35
cjwatsonapt-cdrom-check will show you what it's looking for15:35
* xnox got it.15:36
cjwatsonwell, I've acked the proposed approach on 1013681 now although not the specifics15:37
cjwatsonit's not a security hole as the code is currently disabled, so I'd rather not rush mvo into it; if he's comfortable that what he has now is secure then he should upload it, if not then we can live without it for another release IMO15:38
bdmurrayokay so let's wait on won't fix'ing15:41
bdmurraythat's all I had for today15:41
mvocjwatson: it will require a server side change15:43
mvocjwatson: if you guys are happy with the new proposed schema we can upload (once the server side is updated)15:43
mvobut I (much) agree we should not rush this :) it caused enough pain already :/15:43
cjwatsonOf course I can't help with the server side change at the moment because we don't have our sudo access back yet on pepo15:45
cjwatsonYou'll probably have to ask webops15:45
* xnox got some help with autofs flex parser from mjt =)15:46
* xnox \0/15:46
cjwatson#topic AOB15:47
=== meetingology changed the topic of #ubuntu-meeting to: AOB
cjwatsonxnox: oh good15:47
cjwatsonany more for any more?15:48
evthe 12.10 and 12.04 lines on errors.ubuntu.com have not converged15:49
evand we're getting ever closer to release day15:49
evnot sure how to spin that into a positive :)15:49
infinityAre we expecting them to converge?15:50
evinfinity: I would hope so. It currently implies that 12.10 is less stable than 12.0415:50
infinityA stable release with a ton of post-release bugfixing, versus a new release with a ton of new software and new bugs?15:50
xnoxev: having them no converged is ok, as long as quantal one is below precise..... but that is not the case15:50
xnoxev: having them not converged is ok, as long as quantal one is below precise..... but that is not the case15:51
infinity(I mean, I'd like each release to be better than the last, but right after an LTS and a massive push to stabilise said LTS seems like a bit of a hard benchmark)15:51
evbut surely we don't want to ship something less stable than what we put out previously?15:51
ogra_heh15:51
evone step forward, two steps back and all that15:51
ogra_can we hire 100 more devs then ?15:52
infinityev: I think the only way to guarantee that is to stop fixing bugs in the LTS. :P15:52
* micahg would think that applies LTS -> LTS15:52
* xnox was considering to propose that Debian releases when RC(stable) > RC(testing) for a period of 3+ months....15:52
ogra_micahg, ++15:52
* ev beats ogra_ to death with the mythical man month15:52
micahgor interim -> interim15:52
cjwatsonI can't figure out how to get the table below the graphs to show me just problems in 12.1015:52
TheLordOfTimecjwatson:  on errors.u.c?15:52
cjwatsonYes15:52
evcjwatson: change the "error reports for" to Ubuntu 12.1015:53
TheLordOfTime^ that15:53
TheLordOfTimenear the top of that15:53
TheLordOfTimepage15:53
cjwatsonI do not see a widget labelled thus15:53
cjwatsonThere are clicky things labelled "Ubuntu 12.04" and "Ubuntu 12.10"15:53
evabove that15:53
evto the left15:53
cjwatsonOh I see, duh15:53
cjwatsonThanks15:53
evjust under the site navigation15:53
TheLordOfTime:P15:53
evsure thing15:53
evthat's changing, by the way15:53
evto something you'll presumably find a bit more intuitive15:54
evI'll post the mockup shortly15:54
* xnox presumes cjwatson scrolled down to the table ignoring the pretty pictures and colourful css and then tried to control the table....15:55
evbut it's like jml summarised in that canonical-tech posting:15:55
cjwatsonThe 12.10 list seems pretty dominated by software-center15:55
ev   * Don't show your work-in-progress. Make it look like it came from15:55
evheaven. You aren't going to get a second chance after they use your15:55
evbuggy app.15:55
ev     * Ship 3.0.15:55
=== jacky is now known as jalcine
cjwatsonxnox: No, I was misled by "all installed versions"15:55
evI just don't think it's acceptable that we throw something out there that's less stable than 12.04 just because 12.04 was an LTS15:55
evI have no doubt I'll be overruled on this :)15:55
evbut I want to make that sentiment known15:55
xnoxev: Debian folks will love you =)15:56
evsomehow I doubt that15:56
evDebian folks and I don't generally get along15:56
* xnox remembers something about "time-based releases"15:56
ogra_ev, seriously, the LTS got several extra months of stabilization15:56
slangasekyeah, we Debian folk don't get on with ev15:56
evwhat with my love for our inherited package system and development process15:56
ogra_how could 12.10 even remotely be more stable15:56
evogra_: because we shouldn't be letting things through that make it less stable. 12.04 should be the bar.15:57
infinityev: Generally, I agree with you that each release should be an obvious quality iteration over the last, but the way we did post-release development on the LTS, it's a bit hard to demand that the next non-LTS measure up, bug-wise (though, it should be shinier and featurier!)15:57
ogra_to do a proper comparison here you would have to compare a snapshot of 12.04 that was taken at the same time in the cycle to todays quantal at least15:57
slangasekinfinity: it's not hard at all to demand it, it's just hard to deliver it15:58
infinityev: "Shouldn't be letting things through that make it less stable" means "no new upstream GNOME or KDE" (etc), which just ain't gonna happen.15:58
davmor2ogra_: not switch it on?15:58
evwe shouldn't consider each release independent of one another, otherwise we're always going to be going back and forth between remotely stable and hideously unstable15:58
infinityslangasek: Heh.15:58
slangasekI think we absolutely should demand it ;)15:58
ogra_davmor2, lol15:58
evso for what it's worth, Matthew has asked Rick to make that graph release criteria in the future15:59
ogra_oh my15:59
micahgev: no, but you have to compare apples to apples, 10.04 -> 12.04, 10.10 -> 12.1015:59
ogra_ev, then pretty please sync up the comparison timelines15:59
evmicahg, ogra_: then we'll at best be racing to catch up with the LTS as we get close to it16:00
ogra_you cant really compare something that had 50% more time and work invested into it with something unfinished if you dont look at the same timeframe16:00
slangasekmicahg: why should we tolerate the newer release being crashier than the older one, LTS or not?16:00
evwe won't be getting more stable than the LTS16:00
evand we wont be able to promise stable releases to our users between releases16:00
slangasekogra_: why is "something unfinished" uploaded to the archive? :)16:00
micahgslangasek: because the LTS is feature conservative which starts you out in a better place quality wise16:00
ogra_slangasek, the release as such isnt finished :)16:00
slangasekogra_: right, so you're arguing we should compare 12.10 today with 12.04 at the same point pre-release instead of comparing it with 12.04 today16:01
evwelcome mpt. Thought you might find this chat interesting16:01
ogra_all i'm sayin is that you need to compate precise after 5 months of development with quantal after 5months of development16:01
ogra_else the measuring is nonsense16:01
infinityWe wouldn't need such pesky things as "feature freeze", if every new feature was landed bug-free.  Adding new software will add bugs, period.16:01
micahgeven that might not be a fair comparison16:01
infinityAnd the LTS had 3 months of extra bug-fixing.16:01
slangasekogra_: the point is that we want to be constantly ratcheting up the quality16:01
ogra_*compare16:01
infinity(Heck, it continues to have bug-fixing)16:02
slangasekand not just delivering something that's "as good" at release time as the last one16:02
ogra_slangasek, how if we have a huge dump of new sowftware each cycle that needs stabilization first16:02
evinfinity: sure - but shouldn't we be forward porting those fixes too?16:02
ogra_it will always be a sinus16:02
slangasekand the way to do that is to hold ourselves to a higher standard than what we delivered before16:02
slangasekogra_: by not allowing huge dumps of software still in need of stabilization16:02
evslangasek: ++16:02
infinityev: Old fixes don't magically apply to new features.16:02
ogra_it might raise over tie16:02
micahgright, while there's a 6 mo release cycle, it's really a 2 yr/4 release cycle16:02
infinityev: But yes, where they apply, of course they should be forward-ported and upstreamed.16:03
slangasekanyway, I'm not here today so I should perhaps stop derailing the meeting ;)16:03
evhahaha16:03
ogra_but after all quality will droip through the cycle and has to be re-established every release16:03
cjwatsonOld fixes - our processes tend to ensure this anyway by demanding that fixes land in the development release before being SRUed16:03
cjwatson(except near release)16:03
slangasekogra_: that's the pattern of the past.  I don't think we should accept it as inevitable for the future.16:03
micahgso, each LTS should be progressively better, each LTS + 1 should be progressively better16:03
ogra_slangasek, by doin what ? take over all upstreams ?16:03
ogra_we dont really have any influence here16:04
slangaseksure we do16:04
evmicahg: only if we're chasing quality rather than demanding it up front, the chances of that happening are slim16:04
slangasekwe don't take stuff that's not ready :)16:04
ogra_tricky :)16:04
evmicahg: especially over the distance between LTSes16:04
cjwatsonslangasek: I do think auto-syncs would be completely impractical if we applied that standard in general16:04
cjwatsonWe can do it for stuff we touch anyway16:04
micahgev: it's hard not to break stuff when you land a new everything, I would think the goal is to improve that over time as we have more automated test coverage16:05
evsuddenly in 3 months of LTS development we have to care about getting *better* than the previous LTS was16:05
ogra_note that i dont disagree that quality should raise with each release ... i just dont think the way we measure quality id right here16:05
ogra_*is16:05
xnoxworkitems burn-down chart has negative correlation with positive slope on the the errors chart16:05
micahgev: I would think that each 2yr LTS cycle the quality gets better so you don't have to chase up quality at the last minute16:05
evogra_: what's wrong with how we're measuring it?16:05
ogra_since it doesnt apply to the real world scenario16:05
slangasekcjwatson: yes, another good point16:05
ogra_ev, if you measure R rigth after the big debian import and compare it to quantal final, R will be highly more unstable at that point16:06
infinityev: Well, in an "ideal" world, the number of incidents per day in an LTS should approach 0 as people backport and fix old bugs.  (Sure, it won't reach 0, but that's the goal).16:06
evmicahg: we shouldn't be landing a new everything unless it's not making the line go up. If it does, reject it until we can show that it doesn't affect stability16:06
infinityev: In a new release with new features and new bugs, we can never converge on that line, only on a data point in the past, as Oli points out.16:06
cjwatsonogra_: That will hopefully change as we move to using -proposed16:07
evwe shouldn't be giving people a blanket license to upload whatever broken software they want16:07
evbecause "we'll fix it eventually"16:07
ogra_you need to compare the two points in time, not the final product with a product in the works16:07
cjwatsonThe vast majority of auto-sync breakage is just transient dependency kerfuffle, and that's detectable16:07
evogra_: right, and I'm saying we shouldn't do that.16:07
micahgev: you can't predict every interaction, over time it will get better, but there will be bumps along the way, one would hope that it's new bumps each time though rather than the old ones16:07
xnoxinfinity: well it will reach to 0, because people will upgrade from the LTS to get shiny candy from asterisk or unity or emacs (or whatever tickles their fancy)16:07
ogra_ev, how else will you accurately measure then ?16:07
evif something from an import is proving unstable, kick it out until we can prove otherwise16:07
* cjwatson proposes ev runs the auto-syncs for a while ;-)16:08
infinityxnox: Neat theory, but plenty of people (including us!) still us hardy in production.16:08
ogra_my mom uses hardy :)16:08
infinitys/still us/still use/16:08
xnoxinfinity: i remember upgrading from potato last year....16:08
* ogra_ recently discovered that 16:08
evcjwatson: I'm not saying don't do the autosyncs. I'm saying that if something passes through whatever QA we have and is showing up as buggy on errors.ubuntu.com, and we're not going to immediately fix it, then revert back to the old version.16:09
xnoxev: should we sync from testing by default then? such that we don't get debian's RC bugs, which will put us behind debian in terms of features, as users are free to run debian unstable to get shiny stuff16:09
infinityev: It's also pretty unrealistic (IMO) to say "well, if you land the new GNOME stack and it has new bugs that hurt the pretty graph, we should revert the whole thing until it can all magically be fixed without testers".16:09
evinfinity: why?16:09
ogra_ev, what you are proposing means that every package has to be touched ....16:09
evI just don't think we can accept these as the rules of the game16:09
ogra_no more autosyncing etc16:10
evI realise our tooling isn't entirely there16:10
evbut we should focus on that16:10
infinityev: Hey, if you want to be the one who figures out how to reliably downgrade everyone to an old GNOME version, be my guest.  But that's wasted effort.16:10
infinityev: It's not about "tooling".16:10
evrather than focus on continuing to shovel broken software in and throwing our hands in the air when we talk about being able to revert bad decisions16:10
* ogra_ hands ev the manhour back with the last sentence :P16:10
cjwatsonev: I actually quite seriously think that -proposed will sort out omost of the auto-sync chaos16:10
cjwatsonev: Given that practically none of the stuff we see on errors.ubuntu.com is auto-synced from Debian; it's nearly all Ubuntu-specific stuff16:11
xnoxev: what about facebook style deployements "reverts are for suckers" policy which implies "everyone help fix the last deployment NOW"16:11
evthis is getting slightly off track. It's ultimately unrelated to whether we use those lines as release criteria16:11
evxnox: sure16:11
evthis is why I think we're off track16:11
cjwatsonev: Which has implied to me for some time that worrying about imports of other people's software is misdirected effort, and we need to get our own in-house-developed software in order instead16:11
eveven if we accept broken software into the archive16:11
ogra_xnox, yay, after hours !16:11
evwe should be fixing that *now*16:11
evnot in a few releases16:12
infinitycjwatson: Yeah, I won't disagree with that.16:12
evcjwatson: to be honest, I'd like to get to the point where we can measure the actual usage of this software16:12
evI think a lot of time is wasted on merges and syncs that are done because people can16:12
evand not because anyone is actually using the software16:12
xnoxogra_: well... it all mater only up to... it's time for my volleyball practice. And by that time US folks are up ;-)16:13
evand then we could take the number of people using a package, the number of errors it has, and make a real judgement on whether its worth our investment16:13
ogra_that surely doesnt apply to main16:13
evof qa, engineering, etc16:13
cjwatsonI wonder how much time you think is wasted on auto-syncs; it's not that much16:13
ogra_(or what MoM lists as main)16:13
stgraberwell, if something isn't widely used, it's unlikely to have an Ubuntu delta, so it's just a "free" auto-sync then16:13
xnox"free" auto-sync with bugs.16:13
infinityWe'll sometimes carry a small FTBFS delta, but that's never onerous.16:13
* xnox wanted new offlineimap and I am not affected by it's new bug..... yet everyone else is.....16:14
ogra_stgraber, apart from libs and transitions that come down the drain and need manual intervention on a set of ubuntu maintained bits16:14
infinityAnything with an actual runtime bugfix kinda implies someone used it and found a bug.16:14
stgraberogra_: right, but these are mostly easy/repetitive/scriptable kind of work, not multi-hours kind of merges like we have on some other packages16:15
ogra_yeah, indeed, but its work nontheless and migth have impact on e-u-c graphs16:15
infinityAnyhow, we already spend a majority of our engineering time on a tiny subset of the archive, and most of the time people complain about having to fix a transition or touch a package "that doesn't matter", they could have fixed it in the time it took to whine. :P16:15
cjwatsonI also worry about the underlying notion that even if only 1% of our userbase uses something, say, that we can afford to incrementally annoy 1% of our users in slices until they're all gone16:16
stgraberxnox: for something that doesn't have an Ubuntu delta, I prefer being in sync with Debian so that we can directly forward any bug report there than run an old version that's supposedly more stable (we don't really know) and where when it breaks we'd just be told that we're using an outdated version16:16
evcjwatson: I think the data (if we ever get it) will first show that our userbase isn't a collection of 1% slices16:17
cjwatsonI'd much rather be very inclusive of the long tail16:17
stgrabercjwatson: +1 on the whining is taking up way more time than actually fixing it :)16:17
xnoxstgraber: yeah... I uploaded into debian ;-)16:17
cjwatsonev: I also think that the effort of discussing most of this exceeds the effort involved in leaving it there :-)16:18
ev:)16:18
* infinity thinks that perhaps this meeting has run its course, and it's time for us to plan an in-person sprint, with boxing gloves.16:18
evyes please16:18
cjwatson1% is a random number obviously but I have at least some anecdotal evidence in the form of upset messages in my inbox from a reasonable percentage of the packages I remove from the archive16:18
cjwatsonMany of which I thought were so obscure nobody would care16:19
cjwatsonIt turns out we have users who care about different business-specific requirements ;-)16:19
evcjwatson: we could always work out a system whereby it got copied to another pocket16:19
evinstead of removed entirely16:19
everr moved16:19
evone that our users don't have to deal with16:19
infinityev: That's just adding complexity, I don't see how that fixes anything.16:19
cjwatsonWell, this was stuff that had been removed from Debian, generally16:19
evah16:19
cjwatsonNot removing it means we assume responsibility16:19
slangasekgeez, y'all are still going? :)16:20
slangasek#endmeeting16:20
ogra_haha16:20
infinity\o/16:20
cjwatsonSo I think those removals were generally correct, but even in those should-be-fairly-uncontroversial cases, a good fraction of the removals cause user upset16:20
cjwatson#endmeeting16:20
=== meetingology changed the topic of #ubuntu-meeting to: Ubuntu Meeting Grounds | Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs | Meetingology documentation: https://wiki.ubuntu.com/meetingology
meetingologyMeeting ended Wed Sep 12 16:20:20 2012 UTC.16:20
meetingologyMinutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-12-15.01.moin.txt16:20
meetingologyMinutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-12-15.01.html16:20
cjwatsonThe man's right :)16:20
* cjwatson distracted by argument16:20
infinityI'm going to /part and avoid being suckered into continuing this argument today. :P16:20
stgraber:)16:22
* highvoltage has managed to avoid arguments all day long so far17:33
=== emma is now known as em
=== medberry is now known as med_

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