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

pleia2hi everyone, Americas board meeting should be starting now but it looks like neither of the folks on the list are here at the moment01:00
pleia2kombuchakip? dhillonv10?01:00
pleia2we'll be here for a half hour if either of them comes by, but then we'll have to call it a night01:01
dindapleia2: ok, i01:06
dindapleia2: I'm around if needed01:06
pleia2ok, I'll ping you if they show up :)01:07
* pleia2 has an ubuntu hour to skip off to after the meeting anyway01:07
pleia2ok folks, I think we're going to wrap this up01:30
nhandlerSorry for anyone who showed up to support any of the applicants01:30
pleia2thanks for coming anyway :)01:30
=== Ursinha-afk is now known as Ursinha
=== ptkhanh|zzz is now known as ptkhanh
=== robbiew1 is now known as robbiew
=== doko__ is now known as doko
czajkowski/c09:59
jpds /j10:00
soren/?10:34
=== yofel_ is now known as yofel
pittiskaet: good morning! meeting is in 8 mins, right?14:52
tsimpsonPici: fridge says it stars in an hour14:55
tsimpsonerr, pitti14:55
tsimpson(tab-fail)14:55
Picitsimpson: its okay, I'm used to getting pitti's hilights.14:55
pitti* Time: 1500UTC - 1630UTC14:56
pittithat's what the email invitation said14:56
pitti(and that also was the usual time for many, many months)14:56
pittitsimpson: I guess the fridge isn't UTC based?14:57
=== Ursinha is now known as Ursinha-lunch
tsimpsonpitti: it _should_ be, butt google has UTC fail recently14:57
tsimpsonI think it gets confused about DST changes14:58
apwyep, 15:00 is now15:00
ograpitti, in 1h15:07
ograas usual15:07
pittiogra: depends on the definition of "as usual" :) 1500 UTC was "as usual" during summer15:07
pittiand also in the previous winter15:07
ograwell, i got an invitation from skaet that says 17:00 local time for me15:08
pittigcal is broken15:08
ograi usually trust evolutions TZ translation here15:08
pittiogra: the email invitation said 1500 UTC15:08
ogramore than gcal15:08
apw* Time: 1500UTC - 1630UTC15:08
pittibut anyway, she's not here yet, so I guess we postpone it to later15:08
skaetpitti,  sorry about the calendar glitch.   I was expecting it to start in an hour....15:09
apw apw@dm$ date -u15:09
apwFri Nov 19 15:08:58 UTC 201015:09
apwskaet, that is cause you believed the crap google cal tells you :)15:09
ScottKo/15:09
apwit has never been right since you guys moves the time of the DST transitions off the time the rest of the world does them15:09
skaetapw,  indeed...   silly me,  believing the tools work.   sigh.  should know better.15:09
apw:)15:09
ScottKapw: Well that's over now, so I think that's not it.15:10
apwScottK, is it?  ok15:10
ScottKI think.  Doesn't Europe switch first?15:10
ScottKUS switched last weekend.15:10
ScottK(or was it two weeks, I've lost track)15:10
apwyeah we switched when you used to do ... having aligned with you :)15:11
ScottKOf course.15:11
skaetsee y'all back here in an hour, ok?15:11
ScottKAt least it's not like Argentina where the legistlature has to decide it every year.15:11
pittiskaet: why not start now?15:12
skaetdon't think marjo & victorp are around...15:12
ograpitti, because i have my page not ready yet :P15:12
pittiskaet: if not, do we officially move it later one hour just for today, or for subsequent meetings as well?15:12
victorpskaet - hi15:12
skaetpitti,  all subsequent ones.15:12
victorpmy calendar shows that it starts in 45min15:13
apwskaet, have you checked if the hour after is empty too ?15:13
victorpbusy now15:13
apwvictorp, your calendar is wrong sadly ... google is hopeless with DST handling15:13
victorpapw - yes it is15:13
victorpthe sad fact still remain that I am book in another meeting :)15:14
apwskaet, ok on the fridge its at 16:00-17:00 UTC15:14
* skaet shakes head head - its showing on mine (and I set it, as 10am)...15:16
skaetI'll go in, and re-create it now that all the time zones have settled down, and see if we can get it on everyone's calendar properly.15:17
skaetsorry 'bout the glitch.  :(15:18
skaetpitti, ScottK, ogra, victorp, apw - will see you back here in ~40 mins.    thanks for your patience.15:19
charlie-tcaI am starting to severely dislike these calendars. They seem to fail often15:19
* skaet nods15:19
sorenskaet: Secret trick: If the calendar you're using doesn't let you set UTC as your timezone, try setting it to Iceland. They follow UTC (and have no DST).15:28
sorenskaet: That's TZ="Atlantic/Reykjavik", by the way.15:31
* skaet hugs soren - good tip!15:31
sorenskaet: The problem is if it's been scheduled in a TZ that has DST. Then the UTC time of it changes as that TZ moved in and out of DST. Mass confusion ensues.15:32
=== Ursinha-lunch is now known as Ursinha
* skaet has gone in and recreated the calendar entry - it should be showing up at 16:00 UTC ... fingers crossed.15:57
skaetwhich should be in about 3 minutes from now.....15:57
ogra215:58
ScottK115:59
* marjo waves15:59
skaet#startmeetin15:59
ograGOOOOOO ! :)15:59
* pitti throws a g15:59
skaet#startmeeting15:59
MootBotMeeting started at 09:59. The chair is skaet.15:59
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:59
* joshuahoover waves16:00
skaetmorning all,  sorry about the calendar glitches....16:00
* charlie-tca waves - observing16:00
skaetwelcome to kickoff for Natty release planning.16:01
skaetRelease Schedule: https://wiki.ubuntu.com/NattyReleaseSchedule16:01
robbiewo/16:01
zematynnado/16:02
skaeton the agenda,  there are a variety of actions that have caried over from the UDS BOF.16:02
skaetmost are for me, and are in progress ;)16:02
ScottKskaet: FWIW, I'd prefer the term lessons learned over post-mortem.16:03
skaetjust wondering if anyone had comments about the NattyReleaseSchedule?16:03
skaetScottK,  no problem - will change it.16:03
marjoskaet: another term is "retrospective"16:04
skaetThanks marjo,  will work with "lessons learned",  have heard it used a bit more in other places.  :)16:05
sconklincould you post the agenda link please?16:05
jdstrando/16:05
skaetis cjwatson around?16:05
ScottKskaet: IIRC we were going to add the Linaro freeze to the schedule.16:05
marjosconklin: https://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-11-1916:05
skaethttps://wiki.ubuntu.com/ReleaseTeam/Meeting/2010-11-1916:05
skaetall,  the link is in the meeting invite as well for future reference.16:06
cjwatsonhi16:06
skaetScottK,   Linaro invite is on the NattyReleaseInterlock page16:06
skaethi cjwatson, before natty alpha1, merge cron jobs (still limited cron jobs) - where are we with this?16:07
* skaet just going through the action items, before going into the round table.16:07
cjwatsonskaet: not sure I understand what that means.  do you remember more detail?16:08
ScottKskaet: I'm reasonably certain most people will just look at the release shcedule.16:08
skaetcjwatson, hmm, not handy - will take it up with you offline then.16:08
cjwatsonskaet: if it means cdimage cron jobs, that's all don16:09
cjwatson*done16:09
cjwatsonbut I don't know if that's what it means16:09
skaetScottK,  if so, will work with JamieBennett to get it added in16:09
skaetcjwatson, thats likely it, will double check later.16:09
skaetOn to Team Updates Section now...16:10
ScottKskaet: Is there supposed to be an A-1 work item iteration in the schedule (it seems odd to start with 2)?16:10
ScottKskaet: There was an item in the overview we needed to discuss16:10
ScottKhttps://bugs.launchpad.net/launchpad/+bug/67720916:11
skaetScottK, when I asked about that A-1 vs. A-2, was told we don't make commitments for A-1,  only going in for A-2, which is why its listed as such.16:11
ScottKOK.16:11
pittiwe still use some a1 milestoning for stuff that really needs to land early, FWIW16:12
pittibut that can be considered "team-internal planning" only16:13
skaetScottK,  re: 677290,  cjwatson is aware of it.   Not sure there's a solution known - but agree need to figure something out.16:13
ScottKskaet: OK.  All the items in the related bug are about the bug tracker.  I think that have access to the Ubuntu archive is a rather more urgent and serious matter.16:14
skaetcjwatson, robbiew ?16:14
cjwatsonaye16:14
cjwatson[LINK] http://people.canonical.com/~platform/workitems/natty/canonical-foundations.html16:15
MootBotLINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-foundations.html16:15
cjwatsonMost specs are in place now.  A lot of our work is carried over from previous cycles, so we didn't have so much drafting to do this time round, although there are a few significant additions.16:15
cjwatsonA selection of interesting things that have been happening over the last couple of weeks in foundations, aside from the usual bringing up of the archive, CD images, merges, and the like:16:15
cjwatson * early development work on flicker-free boot16:15
cjwatson * gcc linking changes, dealing with associated build failures16:15
cjwatson * preliminary patches for notifying plymouth about upstart state changes16:15
cjwatson * primary and ports builds consolidated into single directories on cdimage16:15
cjwatson * pushing the grub/btrfs licensing question a bit further up the hill with relevant external licence holders16:15
cjwatson * python2.7 build failure work16:15
cjwatson * software-center ratings-and-reviews work16:15
cjwatson * training new team member on upstart16:15
cjwatsonOne thing I should note is that Ubuntu 10.04.2 is not all that far away.  If you have bugs you want to get fixed there, get them into the SRU process as soon as possible!16:15
cjwatson[LINK] https://launchpad.net/ubuntu/+milestone/ubuntu-10.04.216:15
MootBotLINK received:  https://launchpad.net/ubuntu/+milestone/ubuntu-10.04.216:15
cjwatsonI think that's all16:15
cjwatson677209: I'm going to try changing the owner to ubuntu-archive today16:15
cjwatsonin fact, right now.  let's see what blows up.16:16
* skaet LOL.... wasn't quite ready to go there, but .... ok, lets head in.16:16
cjwatsonoh, sorry!  I thought you were asking for the foundations update16:16
skaetlol16:16
skaetno worries.16:16
marjoskaet: feels like a first release meeting :)16:17
skaet[TOPIC] Team Updates16:17
MootBotNew Topic:  Team Updates16:17
cjwatsonForbiddenAttribute.  poo.16:17
cjwatsonI'll ask for a LOSA to do it.16:17
skaetnext week - concerned that Alpha1  is week after, and its also Thanksgiving weekend.16:17
skaetcjwatson are we in good enough shape, we can cancel the meeting or should I hold it?16:18
pitticjwatson: I guess python2.6 is meant to disappear from a standard install by final natty? or is there a different plan for 2.6/2.7?16:18
skaetAlso,   just want people to know we'll be starting up a bi-weekly meeting to discuss SRU and 10.04.2 LTS next monday, and 10.04.2 won't be covered in this meeting.16:19
cjwatsonskaet: up to you, Thanksgiving doesn't affect me :)16:20
cjwatsonpitti: ScottK will know current thinking better than I.  I think we want to avoid multiple Python versions on the CDs though16:20
ScottKpitti: We need to see how 2.7 goes.  Plan is to make a final decision before feature freeze.16:20
* jdstrand won't be here, but also won't have anything to contribute in the highest of all likelihoods16:20
pittiScottK: so it'll be one or the other?16:20
skaetcjwatson,  ok.   Will cancel it formally, but if it looks like an ad-hoc is needed, we can use this slot, for those around...16:20
ScottKpitti: We may have to support both, but only one needs to be on the CD (although .so duplication in extensions and such will still cost space)16:21
pittiScottK: understood, thanks16:21
skaetOther piece of news,  is that we'll be opening up o-series and p-series as planning place holders in next month.16:21
skaet    * These are for assigning bugs and workitems to (so they don't get lost, and can be revisited in and organized fashion at the start of each cycle).16:21
skaet    * Nothing can be uploaded to o-series (or p-series for that matter) until the start of the next release cycle.16:21
skaet    * More communication will be coming out.16:21
pittiScottK: at least we'll have some more potential space savings for the next cycle again :)16:22
ScottKYep16:22
pittiskaet: \o/16:22
pittigreat help for bug targetting16:22
ScottKbarry has been discovering some undocumented gotchas in 2.7, but nothing that's a show stopper so far.16:22
skaetpitti: indeed.   :)    Thanks to jml and launchpad team for helping with this.16:22
skaetok... moving on to the roundtable...16:23
skaet[TOPIC] QA update16:23
MootBotNew Topic:  QA update16:23
marjohi folks!16:23
* skaet o/16:23
marjoin case you missed the memo, Quality Is A Major Focus For Natty!16:23
marjo* Blueprints Review16:24
marjoAll blueprints and work items approved and some already done.16:24
marjohttp://people.canonical.com/~pitti/workitems/natty/canonical-platform-qa.html16:24
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/natty/canonical-platform-qa.html16:24
* pitti makes a note that work item chart URLs sohuld use ~platform now16:24
marjopitti: ack16:24
ograbut but ... the credits !16:24
marjo* Would like to introduce Jean-Baptiste Lallement (jibel). He's taken over testing lead from ara. Thank you to ara for all her excellent work in previous releases!16:24
skaetthanks ara, and welcome jibel   :)16:25
jibelHi all16:25
marjo* Natty Test Plan16:25
marjohttps://blueprints.launchpad.net/ubuntu/+spec/other-qa-n-testplan16:25
marjohttps://wiki.ubuntu.com/QATeam/NattyTestPlan16:25
marjoPlease review and provide feedback; it's not too late16:25
skaetmarjo,  will do.  thanks.16:26
marjoAs part of jibel's work, please take a look at the following16:26
marjo* Desktop Automated Testing Results16:26
marjo http://reports.qa.ubuntu.com/reports/desktop-testing/natty/#unity16:26
marjoi think it's quite a nice format, but as usual, if you have any enhancement requests, please just ask16:27
pittithat's quite impressive!16:27
marjowe want the QA reports to be useful and meaningful so we can use the data for decision making16:27
pittilots of script errors, but I guess these are being worked on?16:28
marjopitti: i agree and thx on behalf of the qa team16:28
marjopitti: ack16:28
fader_Minor suggestion: it might be nice to highlight failed cases a bit more (change the color of the number or the background of the table cell?)16:28
pittimarjo: can we link failures with bugs?16:29
marjofader_ ack and thx16:29
pittifader_ +116:29
marjopitti: have received similar suggestion from skaet16:29
marjowill consider both to make it easy to link failed tests directly to bug reports16:29
skaetmarjo, is everything ready to start the testing  of the alpha1 images, the week after next?16:29
jibelpitti, thats mainly scripts that are not compatible with unity (app menu, indicators, ...) they need a rewrite.16:29
pittijibel: ah, I see16:30
marjoskaet: yes, will be ready, mostly setting up iso tracker (that's SOP)16:30
skaetmarjo, jibel:  cool.  :)16:30
skaetany other questions?16:31
marjohere's the QA Dashboard16:31
marjohttp://people.canonical.com/~marjomercado/qadashboard.html16:31
MootBotLINK received:  http://people.canonical.com/~marjomercado/qadashboard.html16:31
marjoIt's under development, so looking for feedback as always16:32
marjoskaet: that's it from QA team16:32
* skaet looks around for hands...16:32
marjothx all!16:32
skaetthanks marjo.16:33
apwskaet, ? hands for ?16:33
charlie-tcao/16:33
skaetraising hands for questions....  ;)16:33
* charlie-tca raises hand16:33
* apw looks stupid16:33
skaetcharlie-tca, goahead, then we'll move on to Hardware Cert16:34
charlie-tcaIt seems like it is going to be hard to test alpha1 for accessibilty, since I don't have a good image to even complete a test case yet16:34
charlie-tcaIs that something that was planned for alpha1 or 2?16:35
dbarthcharlie-tca: do you mean with unity or the classic desktop?16:36
marjocharlie-tca: if necessary, can postpone to alpha-216:36
dbarthunity won't have a11y support until a216:36
cjwatsongood image> what's the problem?16:36
apwin what way is the image not good ?16:36
charlie-tcaeither. Classic and unity are both failing right now16:36
marjoif functionality not there16:36
charlie-tcait doesn't install/login16:37
cjwatsonperiod, or just with a11y?16:37
charlie-tcaNatty won't install with nvidia at all16:37
cjwatsonanyone know if this is just a general problem?16:37
cjwatsonI can try a kvm test today16:37
apwcharlie-tca, bug number ?16:37
charlie-tcaalso won't login for most of us if we do get it to install16:37
charlie-tcaduh16:38
cjwatsonif the images are just entirely broken then obviously we need to fix that for a116:38
apwcjwatson, i've booted but not installed the lives from a couple of days ago16:38
charlie-tcaI don't have the bug number16:38
pitticjwatson: yesterday's image just loops with X start in kvm, haven't had time to investigate yet16:38
pittiand I didn't try yet on real iron16:38
apwpitti, that is a kernel issue, and only affects kvm16:38
apwwe have the fix committed for that16:38
pittiah, cool16:38
charlie-tcaI can get a desktop, but can not run the install. It fails everytime. I will run it again and get a bug for it16:38
skaetcharlie-tca, cjwatson, apw - is Bug #661568 related?16:39
tgardnerapw, should we respin natty rather then wait for -rc3 ?16:39
ubottuLaunchpad bug 661568 in nvidia-graphics-drivers-173 (Ubuntu Natty) "nvidia-173 pulls in postfix" [High,Triaged] https://launchpad.net/bugs/66156816:39
charlie-tcano16:39
cjwatsonfixing kvm asap would be good, I do 95% of my development testing there16:39
apwtgardner, am now thinking i should yes, likely we'll get an -rc by monday16:39
cjwatson(though obviously not a whole lot just recently)16:39
charlie-tcaMy original question was a11y. Got that answer.16:39
tgardnerapw, I can take care of it.16:40
apwtgardner, will push that today16:40
skaetokie.   Looks like it surfaced a bigger problem though... so thanks for raising ;)16:40
skaetmoving on...16:41
skaet[TOPIC] Hardware Certification  - victorp?16:41
MootBotNew Topic:  Hardware Certification  - victorp?16:41
victorpyes16:41
victorpI guess I can give you a quick summary of what our plans are16:41
skaet:)16:42
victorpwe plan to start doing *weekly* testing for Natty starting after alpha116:42
victorpthe reason for moving from daily to weekly is that we were not finding as many bugs as we should and we are going to concentrate on improving that16:42
victorpwe are also doing SRU testing for maintenance releases so all of that needs to be juggle on the same lab time16:43
victorpwe are creating a gcal to track what happens when16:43
victorpalso we are trying to consolidate all our reporting into a generic hw-cert account on people.c.c16:43
victorpthat is about it16:44
victorpah yes, we will also do boot metrics16:44
skaetvictorp, will you be doing a run with the candidate images, before Alpha1, - so we get a baseline with it?16:44
victorpskaet: we could, although I was expecting Alpha1 to be the baseline16:45
victorpwe need some stability before we can do automated testing on large amount of systems16:45
victorpalso - on the people side of things, Ara will be the lead16:46
victorpbut she is travelling today16:46
skaetvictorp,  it would be good to do a sample of them at least - so we know where we are and can warn folks if necessary.16:46
victorpskaet - everything is negotiable ;)16:46
victorpok - if you believe there is value lets work together to schedule some16:46
skaetvictorp,  :)    Thanks!16:47
skaetany other questions?16:47
* skaet looks around for o/ s ;)16:47
skaet[TOPIC] Security Team - jdstrand16:48
MootBotNew Topic:  Security Team - jdstrand16:48
jdstrando/16:48
jdstrand[LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty16:48
MootBotLINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Natty16:48
jdstrand[LINK] http://people.canonical.com/~platform/workitems/natty/canonical-security.html16:48
MootBotLINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-security.html16:48
jdstrandOur bps and work items should be up to date. With the exception of apparmor items, most of our work for this cycle came from bringing forward lucid and maverick bps that were postponed.16:48
jdstrandthough apparmor did have several brought forward too...16:49
jdstrandBeyond that, there is not a lot to report. Kees is reworking the packaging on AppArmor and fixing various 2.6 bugs (this is part of our long term goal/hope to get apparmor in Debian). jjohansen and I are looking at ipc mediation and dbus confinement, and as a team we are getting to our merges and security fixes for natty.16:49
skaetthanks jdstrand.  :)16:49
skaetany questions?16:49
skaet[TOPIC] Kernel Team Update - apw16:50
MootBotNew Topic:  Kernel Team Update - apw16:50
apwo/16:50
skaet:)16:50
apwOverall status is reported at the first link below.  Burn down for the release is at the second link below.  Burndown for the cycle is at the third link:16:50
apw[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty16:50
apw[LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-natty-alpha-1.html16:50
apw[LINK] http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg16:50
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Natty16:50
MootBotLINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team-natty-alpha-1.html16:50
MootBotLINK received:  http://people.canonical.com/~platform/workitems/natty/canonical-kernel-team.svg16:50
apwThe burndown is still in flux as new work items are still appearing which is affecting the overall burndown line.  This should resolve in the next week.16:50
apwOf the bugs called out on the agenda the first is actually an ARM bug.  Of the remainder investigation is ongoing, fuller details are available on the status page (first link above); all seem to be limited to a small number of users.  The main distro blueprints are all at a very early stage but progress is being made, everything planned for natty-alpha-1 seems to be on track currently.16:51
apwThe main distro kernel is now rebased forward to mainline v2.6.37-rc2 and uploaded.  Recent updates have re-enabled aufs support and the live-cds are now booting succesfully (at least for i386 and amd64).  Which ARM kernels we will have and at which versions are still in the air at this time.16:51
apw<done>16:51
skaetapw,  thanks.   :)   will adjust the tracking of that first bug.16:51
skaetany questions?16:52
ograthat bug should also be whishlist ;)16:52
skaet[TOPIC] Foundations - cjwatson  ( see above log )16:53
MootBotNew Topic:  Foundations - cjwatson  ( see above log )16:53
ogra(not a critical SRU task)16:53
skaetogra, ack.16:53
skaetthere were some questions on the foundation team's status already above.16:54
davmor2cjwatson: just to confirm charlie-tca issues on the installs. I left a note on #ubuntu-release last night,  for me plymouth doesn't seem to stop,  All I get is the Ubuntu and the dots below cycling.  If I drop into tty I can stop plymouth and manually start gdm but gdm doesn't appear.   I then ran out of time to do anything and have been too busy today16:54
skaetany other questions, comments?16:56
skaetmoving on then...16:56
skaet[TOPIC] Server team update - robbiew?16:56
MootBotNew Topic:  Server team update - robbiew?16:56
robbiewnot much to update in this week16:57
robbiewsorting out blueprints16:57
robbiewmostly done there16:57
robbiewhave prioritized16:57
robbiewbut still need to finish up targeting to milestones16:57
robbiewhttps://wiki.ubuntu.com/ServerTeam/NattyBlueprints16:57
skaetthanks16:58
robbiewplan to work on a REAL status page for next time16:58
robbiew;)16:58
skaet:)16:58
skaetany update on bug#600174?16:58
cjwatson600174 looks like a server bug?17:01
cjwatsonoh, sorry, we moved on to server already17:01
skaet:)17:01
cjwatsondavmor2: thanks17:01
skaetany other questions for server team?17:02
* skaet notes she needs to pick up pace... meeting running long.17:02
skaet[TOPIC] Desktop Team Update  - pitti?17:03
MootBotNew Topic:  Desktop Team Update  - pitti?17:03
pittiMost blueprints are drafted, approved, and have proper WIs, except for:17:03
pitti- other-desktop-n-set-default-paper-size-correctly: Needs lots of research, will probably not make natty in its entirety17:03
pitti- appdevs-desktop-n-app-sandbox: Allison Randal's spec, just landed under the desktop umbrella, but not being worked on by the desktop team17:03
pitti- packageselection-desktop-n-donations-for-free-software-through-software-center: Being worked on by foundations and online services17:03
pittiWe are on track for natty WIs so far.17:03
pittiAlpha-1 chart is a bit behind, but we expect to land the WIs in time still. This particularly affects the unification of desktop and netbook seeds/CDs, and landing the new compiz-based Unity (which is happening as we speak).17:03
pittie already landed the new compiz 0.9, which broke everyone's configuration and key bindings, but will give us early feedback about hardware compatibility and performance.17:03
pittiOn that front, I bootcharted compiz 0.9, and it's quite a bit faster than 0.8 (maverick) indeed, mostly due to not having to parse tons of XML.17:03
pittittps://wiki.ubuntu.com/DesktopTeam/ReleaseStatus has the details about the currently tracked RC bugs.17:03
skaetcool17:03
pittisorry,17:03
pitti[LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus17:04
MootBotLINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus17:04
pittiWrt. CD space savings, all planned package mangling stuff is in now, and reasonably working. On that front we mainly need package rebuilds now.17:04
pittiPerl elimination has turned out to be much harder than anticipated; first because it's against the spirit and letter of the Debian Perl policy, and also raised some discussion with upstream. Hardest problem here is apparmor-utils, which has a very long perl lib dependency chain. So let's not count on Perl removal in Natty, but I think the current optimizations should already get us quite far.17:04
skaetok17:04
skaetany update on the bugs listed in the agenda?17:05
pittiskaet: they are in the wiki page17:06
pittido you want me to paste?17:06
pittithere is nothing that stands out as a blocker or discussion worthy IMHO17:06
skaetpitti,  no need.   Will read up after the meeting.17:06
skaetjust needed to know if blocker or discussion worthy ;)17:06
skaetthanks pitti17:06
skaetany other questions?17:07
skaet[TOPIC] Ubuntu One Team17:07
MootBotNew Topic:  Ubuntu One Team17:07
joshuahoover[LINK] https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus17:07
MootBotLINK received:  https://wiki.ubuntu.com/UbuntuOne/NattyReleaseStatus17:07
joshuahooverno big news to share...details are in the link above...17:07
joshuahooverwork on desktopcouch, choosing which folders to sync on each computer, and integration with zeigeist is all actively in-progress17:07
joshuahooverthe other blueprints are either being finalized or are in queue to be worked on next17:08
joshuahooverour burndown charts will be fixed after today (need to create proper source tasks)17:08
joshuahooverthat's about it17:08
joshuahooverany questions?17:08
skaetthanks joshuahoover :)17:08
dbarthjoshuahoover: are you guys using libzg btw? ie know that it's moving to gdbus?17:08
joshuahooverdbarth: not sure, i'll have to check17:09
dbarthjoshuahoover: get in touch with kamstrup, he'll tell you all about it17:09
joshuahooverdbarth: cool, thanks!17:09
* skaet looks around for more questions...17:09
skaetok, moving on...17:10
skaet[TOPIC] Kubuntu team update17:10
MootBotNew Topic:  Kubuntu team update17:10
skaetScottK or Riddell - who's doing the honors?17:10
Riddell * Qt 4.7.1 and QtWebKit 2.1 in17:10
Riddell * ScottK still working on ARM workaround for Qt17:10
Riddell * Experimentally swiched to gstreamer for phonon backend17:10
Riddell * turned on Raster painting engine in Qt17:10
Riddell * KDE SC 4.6 beta 1 due next week17:10
Riddell * https://wiki.kubuntu.org/Kubuntu/Todo17:10
Riddell we fixed one problem with Qt on ARM but now there's another it seems17:11
ScottKQt is fixed, but GCC is broken and it's Qt that suffers.17:11
ograpoor gcc everyone blames it :)17:12
skaet:)17:13
skaetthanks Riddell.  any questions?17:13
skaet[TOPIC] Desktop Experience17:14
MootBotNew Topic:  Desktop Experience17:14
dbarthhi17:14
skaethi17:14
dbarthThe status report is at: https://wiki.ubuntu.com/DesktopExperienceTeam/NattyReleaseStatus17:14
dbarththe details are there but in general17:14
dbarthblueprints and milestones set in details for the next 2 iterations17:14
dbarthUnity landed today in Natty17:14
skaetcool.17:15
dbarthyeah :-)17:15
dbarthwe're on track with the feature dev. to have all of the launcher and panel again with the compiz version17:15
skaetlet the testing begin....17:15
dbarthtry it out, you'll see how faster it is17:15
dbarthat the Unity Foundations level (aka Ayatana)17:15
* ogra would like to see if it works with GLES :)17:15
dbarththe work on porting dbusmenu over to gdbus is almost finished17:16
dbarthlibzg is ready; dee to follow17:16
dbarthogra: yeah, again patches welcome17:16
dbarthlast17:16
dbarthQA: we've connected the dots i think with the QA team17:17
dbarthand the integration of test plans and teams is going well17:17
* ogra isnt a graphics developer else i would be in another team ;)17:17
marjodbarth: ack & thx17:17
dbarthand on the HW front, we should do the same with victorp next week to make sure we track the compatibility of Unity on a wide range of machines17:18
skaet:)17:18
skaetthanks dbarth.     any questions?17:18
dbarthand we have tarmac and daily builds running now17:18
* skaet oops...17:18
dbarththat's it for DX17:18
dbarth;)17:18
skaetthanks dbarth,  sorry about being too quick there...17:19
skaetany questions?17:19
dbarthnw17:19
skaet[TOPIC] User Experience Team Update17:19
MootBotNew Topic:  User Experience Team Update17:19
* skaet looks around.. not sure we've got representation here....17:20
skaet[TOPIC] ARM team Update - ogra17:20
MootBotNew Topic:  ARM team Update - ogra17:20
ograwiki https://wiki.ubuntu.com/ARMTeam/ReleaseStatus/Natty17:21
ograthe team was mostly busy with spec preparation and writing17:21
ograOMAP4 daily images build again after Bug 674146 was worked around temporary17:21
ograOMAP3 kernel status is not clear yet, while we would like to use linaros kernel, we need confirmation from kernel and security teams for 18 months support17:21
ograSwork on SRU bugs has been done17:21
ograThe FTBFS list on qa.ubuntuwire.org/ftbfs is full of KDE issues caused by Bug 673085 (thanks ScottK for working on a fix)17:21
ubottuLaunchpad bug 674146 in gcc-4.5 (Ubuntu Natty) "dpkg segfaults during debootstrap on natty armel" [High,Confirmed] https://launchpad.net/bugs/67414617:21
ograThe dove architecture has officially been dropped out of official archive builds17:21
ubottuLaunchpad bug 673085 in Linaro GCC "Qt/KDE fails to build on ARM without implicit-it=thumb" [Undecided,New] https://launchpad.net/bugs/67308517:21
ograimage status:17:21
ograthey are building, not much QA has been done at this state of the release17:21
ograspecs:17:21
ograEntire http://people.canonical.com/~platform/workitems/natty/canonical-arm.html17:22
ograA1: http://people.canonical.com/~platform/workitems/natty/canonical-arm-natty-alpha-1.html17:22
ograBugs:17:22
ogramainly SRU bugs we are working on17:22
ograthats it :)17:22
skaetthanks ogra.  :)    questions?17:23
skaet[TOPIC] MOTU Team Update - ScottK17:23
MootBotNew Topic:  MOTU Team Update - ScottK17:23
ScottKHello17:23
skaetHello17:23
ScottKLots of enthusiasm about working on fixing stuff for the toolchain changes on Natty.17:24
skaetcool17:24
ScottKI think a number of people have their head around the no indirect linking changes and are helping others learn how to fix them.17:24
skaetthat's nice to hear.17:25
ScottKI'm a bit concerned about the changes to -no-as-needed where order now matters in a way it didn't before.17:25
ScottK(sorry, I'm a bit fuzzy on the details myself)17:25
skaetI'm not sure I understand...17:25
ScottKIt would be useful if someone who really understands the issue would write up a tutorial.17:25
ScottKThere was another change added to linker behavior where it's pickier about the order now.17:26
ScottKcjwatson: can you help me here?17:26
cjwatsonbasically symbols are processed left-to-right17:26
cjwatson(traditional unix linker semantics)17:27
ScottKAs is usual with gcc, it's just now enforcing what was always that "correct" way to do it, but a lot of sofware is buggy and I don't think people know how to deal with it.17:27
cjwatsonif you have foo.c which uses symbols from libbar, then the link line needs to be foo.c -lbar not -lbar foo.c17:27
ScottKYes.  That's the one.17:28
cjwatsondoko did say that he might turn it off, but I think it would be good to leave it in place for a while17:28
cjwatsonit's not as though the changes are making software worse17:28
skaetdoes it make sense to ask doko to do a write up, we can point folks to?17:28
ScottKIt would be nice if someone who understands this well would write up a tutorial on it.17:28
ScottKcjwatson: I'm not arguing to turn it off at this point, I'd like to do what we can to broaden the set of people that can help fix things.17:29
skaet[ACTION] skaet - find someone to write up a tutorial on increasing strictness of linker and ways to fix it.17:30
MootBotACTION received:  skaet - find someone to write up a tutorial on increasing strictness of linker and ways to fix it.17:30
ScottKThanks.17:31
ScottKThat's all.17:31
* skaet hmm, should probably rephrase the action a bit more, but that's the jist. ;)17:31
skaetthanks ScottK.17:31
skaetany questions?17:31
skaet[TOPIC] Linaro Update - JamieBennett?17:31
MootBotNew Topic:  Linaro Update - JamieBennett?17:31
JamieBennettAll it quiet in Linaro land :)17:32
skaetcongrats on getting the release out :)17:32
JamieBennettThanks !17:32
skaetquiet is good.17:32
JamieBennettNo images atm and lots of work on planning17:32
skaetwhen and where will your blueprints be available?17:32
JamieBennettThey are spread over several projects, not ideal17:33
cjwatsonskaet: http://wiki.debian.org/ToolChain/DSOLinking covers most of it, but the ordering issue needs to be added17:33
JamieBennettwe are writing a tool to collate and show this information17:33
skaetcjwatson,  thanks!17:33
JamieBennettSo lots of work-item-tracker changes are planned17:33
cjwatsondoko: ^- could you make sure the ordering issue shows up in ToolChain/DSOLinking at some point?17:33
skaetJamieBennett, cool.   Looking forward to seeing the collated info.17:34
JamieBennettskaet: yeah, if the tracking stuff comes off soon, we should have some really good tools17:34
skaetexcellent - bounce me a link, when you've got some prototypes.   :)17:34
JamieBennettwill do17:35
skaetthanks JamieBennett.17:35
skaetany questions?17:35
skaet[TOPIC] open floor - new issues, questions, etc. ....17:35
MootBotNew Topic:  open floor - new issues, questions, etc. ....17:35
skaetsorry all about the google calendar glitches.   Can anyone confirm for me, its now correct in Europe and UK?17:36
* skaet looks around....17:37
skaetok,   feels like this meeting should end then now.17:37
pittiif 1600 UTC is supposed to be the new meeting time, it looks correct to me now17:37
skaetthanks pitti.   yup,  thats what we were aiming for.17:38
=== cking is now known as cking|food
pitti(but please let's move it back again in March, otherwise this will go too much into Friday evening)17:38
skaetpitti.   ok. will do.  :)17:38
pittithanks everyone!17:38
skaetthanks everyone.17:38
skaet#endmeeting17:38
MootBotMeeting finished at 11:38.17:38
skaetthanks everyone.   Sorry it ran so late today.17:39
marjothx skaet17:40
skaetthanks marjo17:40
* skaet has put on her thinking cap, and will try to get this a little more efficient next time.17:41
marjoskaet: don't let the qa guy run on and on17:41
skaetlol17:41
marjoskaet: he likes to ask for feedback17:42
skaet:)17:42
* skaet heading off for some lunch now...17:43
=== cking|food is now known as cking
=== Ursinha is now known as Ursinha-afk
=== bjf is now known as bjf[afk]
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha
=== Ursinha is now known as Ursinha-afk

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