[16:00] <utlemming> o/
[16:00] <arosales> Hello
[16:01] <arosales> hopefully folks have gotten some rest from ODS
[16:01] <jamespage> o/
[16:02] <zul> oh right there is a meeting today
[16:02] <zul> who is suppose to be running it
[16:02] <SpamapS> I should
[16:02] <SpamapS> I skipped so many
[16:02] <SpamapS> though smoser is on the list
[16:02] <arosales> Ursinha: chair'ed last week
[16:02] <SpamapS> smoser: 30 seconds to object...
[16:02] <arosales> and smoser before her
[16:02] <SpamapS> ahh
[16:03] <SpamapS> nobody is updating the agenda
[16:03] <arosales> utlemming: is up on the list, but I am sure he would let SpamapS host
[16:03] <utlemming> SpamapS: I was supposed to chair, but if you want to, I won't object
[16:03] <SpamapS> indeed, the header says 2012-04-10
[16:03] <SpamapS> #startmeeting Ubuntu Server Team
[16:03] <meetingology> Meeting started Tue Apr 24 16:03:31 2012 UTC.  The chair is SpamapS. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:03] <meetingology> Available 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 #votesrequired
[16:03] <SpamapS> and so we begin :)
[16:03] <arosales> SpamapS: sorry, I should be better about updating the wiki
[16:03] <SpamapS> arosales: its the chair's responsibility, not yours
[16:04] <hallyn> and documented on the knowledgebase very well
[16:04] <arosales> ah, ok
[16:04]  * arosales doesn't feel as bad :-)
[16:04] <SpamapS> #topic Action points from last meeting
[16:04] <hallyn> but maybe we're not informing ppl of that
[16:04] <SpamapS> SpamapS invite aquette to next server team meeting to discuss servercloud-p-cloud-power-management
[16:04] <SpamapS> hallyn: indeed
[16:04] <SpamapS> too late for that, its officially "off the list"
[16:04] <SpamapS> jamespage to raise bugs for FTBFS for server related packages from latest rebuild test.
[16:05] <jamespage> SpamapS, no longer required
[16:05] <SpamapS> brilliant
[16:05] <jamespage> thats really old
[16:05] <smoser> o/
[16:05] <SpamapS> #topic Precise Development
[16:05] <SpamapS> Aren't we like, done?
[16:05] <jamespage> i'd hope so :-)
[16:05] <SpamapS> done or not, we're moving on :)
[16:05] <SpamapS> anybody have something to bring up re the release that happens in 2 days?
[16:05] <jamespage> do lots of testing
[16:06] <arosales> 7 bugs on http://reports.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
[16:06] <hallyn> bottoms up?
[16:06] <arosales> release notes these ?
[16:06] <SpamapS> or SRU them
[16:06] <SpamapS> we'll go over them for that purpose alone
[16:06] <SpamapS> bug 928990
[16:06] <arosales> any of these we should make users aware of as we release?
[16:06] <smoser> jamespage, marked that one as wont-fix i think.
[16:06] <smoser> and moved to that new Q
[16:07] <SpamapS> says Triaged now
[16:07] <smoser> well, its triaged for Q. wont-fix for precise
[16:07] <SpamapS> ah the report is picking up the wrong status
[16:07] <jamespage> smoser: I did start reviewing them this morning
[16:07] <SpamapS> who maintains that report?
[16:07] <utlemming> its marked for Quantal
[16:07] <SpamapS> bug 930916
[16:07] <jamespage> anything that won't be fixed for precise and won't be SRU's should be pushed to Quantal IMHO
[16:07] <SpamapS> Ugh thats me, I kept deferring. I'll see if I can get a near-0-day SRU for that
[16:08] <SpamapS> bug 974613
[16:08] <jamespage> adam_g, is that one fixed with the change you made to the way glance upgrades?
[16:08] <adam_g> jamespage: yes
[16:09] <adam_g> jamespage: ill mark accordingly with a note
[16:09] <SpamapS> woot
[16:09] <SpamapS> bug 974584
[16:09] <hallyn> fixed in precise
[16:09] <hallyn> open for quantal
[16:10] <SpamapS> errr
[16:10] <SpamapS> no
[16:10] <SpamapS> there is nothing fixed in precise that will not also be fixed in quantal
[16:10] <SpamapS> hallyn: can you look at the sysvinit status and see if thats valid?
[16:10] <hallyn> fine.  fixed for lxc.  open for initscripts in quantal
[16:11] <SpamapS> hallyn: ah, so it was worked around in precise
[16:11] <SpamapS> bug 880339
[16:11] <hallyn> yes
[16:11] <SpamapS> still no feedback from the user... but I'm pretty sure we can just close that, all testing I've done shows a working system on upgrade from 11.10 -> 12.04 w/ mysql installed
[16:12] <SpamapS> bug 907197
[16:12] <jamespage> ditto - still waiting for feedback from original reporter
[16:12] <SpamapS> bug 901881
[16:13] <zul> quantal
[16:13] <zul> or sru
[16:13] <SpamapS> zul: does it need a release note?
[16:13] <zul> i dont think so
[16:13] <SpamapS> zul: how about, quantal *and* sru ?
[16:13] <SpamapS> http://status.ubuntu.com/ubuntu-precise/ubuntu-server.html
[16:14] <arosales> So possible known issues to document in the release notes would just be  bug 928990?
[16:14] <SpamapS> pretty steady push of getting things done everybody
[16:14] <zul> SpamapS: that would be good idea
[16:14] <utlemming> aroslaes: I don't think it needs to be documented. The issue is really about needing a rescue console. The behavior here is no different than a phyiscal server.
[16:14] <smoser> arosales, we can document that, thats fine. but it is present sense 10.04
[16:15] <SpamapS> Please take a moment today to go through the blueprints you own and make sure all the work items are POSTPONED or DONE ..
[16:15] <SpamapS> helpful btw, http://status.ubuntu.com/ubuntu-precise/u/launchpad-username.html
[16:15] <arosales> smoser: utlemming: I'll confirm with you guys before suggesting any additions to the release notes, and what the wording should be if it does need to be documented
[16:16] <smoser> k
[16:16] <arosales> roaksoax:  are items hwere going to be postponed: https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-orchestra
[16:16] <SpamapS> Anything else?
[16:17] <SpamapS> arosales: at this point, *everything* is POSTPONED
[16:17] <arosales> SpamapS: ah, gotcha
[16:17]  * roaksoax looks
[16:17] <SpamapS> there is no more doing, only postponing :)
[16:17]  * arosales just seconds folks to udpate their blueprints
[16:17] <hallyn> don't we have 2 mor days?
[16:17] <SpamapS> hallyn: not really
[16:18] <hallyn> surprised
[16:18] <SpamapS> universe freezes today
[16:18] <SpamapS> 1600 UTC
[16:18] <SpamapS> ok moving on
[16:18] <hallyn> (n/a)
[16:18] <ScottK> freezes/froze
[16:19] <SpamapS> true
[16:19] <SpamapS> :)
[16:19] <SpamapS> #topic Ubuntu Server Team Events
[16:19] <arosales> Sounds like ODS went well
[16:20] <arosales> m_3 @ railsconf (http://railsconf2012.com/) 23 -25 April
[16:21] <SpamapS> UDS in 2 weeks!
[16:21] <SpamapS> #topic Weekly Updates & Questions for the QA Team (hggdh)
[16:21] <SpamapS> hggdh: how's 12.04 looking?
[16:22] <hggdh> nothing from me, fully immersed on 12.04 testing
[16:22] <hggdh> seems good so far :-)
[16:22] <SpamapS> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:22] <SpamapS> smb: anything to report?
[16:22] <smb> Already that time... hm not really, lots of testing around but nothing specific
[16:22] <smb> ..
[16:23] <SpamapS> smb: thx
[16:23] <SpamapS> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:23] <rbasak> Nothing to report. Any questions for me?
[16:25] <rbasak> I'll take that as a no.
[16:25] <SpamapS> sorry
[16:25] <SpamapS> #topic Open Discussion
[16:25] <rbasak> Bug 974218 may break upgrades from lucid to precise for users with bonded interfaces, causing the server to fail to bring interfaces up on boot due to a race condition. This is difficult or impossible to reproduce, but based on the reports I think it might be worth release noting. Any thoughts on this?
[16:26] <arosales> seems like a good candidate for release notes --> known issues
[16:28] <SpamapS> another thing, UDS blueprints
[16:28] <rbasak> The trouble is that I'm not sure how much of an issue it is. But it does seem to be a valid problem, and the impact is severe for those affected.
[16:28] <rbasak> (easy workaround though)
[16:28] <SpamapS> Make sure if you have a blueprint that everybody can come ready to discuss. Do not shy away from starting a discussion *now* on ubuntu-devel or ubuntu-server.
[16:28] <jamespage> arosales, rbasak: I think its worth a mentio
[16:29] <jamespage> n
[16:29] <SpamapS> agreed
[16:30] <rbasak> OK I'll flesh out the bug and send something to arosales then?
[16:30] <SpamapS> #action rbasak add bug 974218 to precise release notes
[16:30] <meetingology> ACTION: rbasak add bug 974218 to precise release notes
[16:30] <arosales> rbasak: yes, please send to me and I'll work with the release team to document
[16:30] <rbasak> OK
[16:30] <arosales> Any other release notes items?
[16:31] <zul> that we are awesome
[16:31] <arosales> zul: that has already been there since alpha 1
[16:31] <jamespage> arosales, where can we see the current release notes?  its hard to remember what already went in
[16:31] <zul> oh good....no other words are needed then
[16:32] <arosales> here is the landing page for most things related to the release
[16:32] <arosales> https://wiki.ubuntu.com/PrecisePangolin/
[16:32] <arosales> release notes --> https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes
[16:33] <arosales> I have a few changes I need to make
[16:33] <arosales> but if any one has any data to add please feel free
[16:33] <arosales> Ubuntu Server is specifically @ https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuServer
[16:33] <arosales> ..
[16:34] <jamespage> does someone have something for the squid -> squid3 config transition stuff as its not automated...
[16:36] <arosales> adam_g: I think you were doing some work their
[16:37] <adam_g> jamespage: what do you mean?
[16:37] <adam_g> oh, release notes..
[16:38] <SpamapS> Ok, if thats all then?
[16:38] <SpamapS> #topic Announce next meeting date and time
[16:38] <SpamapS> Next meeting will be next Tuesday, May 1, at 1600 UTC, right here in #ubuntu-meeting
[16:38] <SpamapS> #endmeeting
[16:39] <meetingology> Meeting ended Tue Apr 24 16:38:59 2012 UTC.
[16:39] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-24-16.03.moin.txt
[16:39] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-24-16.03.html
[16:39] <arosales> thanks for chari'ing SpamapS
[16:39] <arosales> chair'ing, that is
[17:00] <jsalisbury> #startmeeting
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <jsalisbury> ##
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <meetingology> Meeting started Tue Apr 24 17:00:03 2012 UTC.  The chair is jsalisbury. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[17:00] <meetingology> Available 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 #votesrequired
[17:00] <jsalisbury> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <jsalisbury> # Meeting Etiquette
[17:00] <jsalisbury> #
[17:00] <jsalisbury> # NOTE: '..' indicates that you are finished with your input.
[17:00] <jsalisbury> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <jsalisbury> Roll Call for Ubuntu Kernel Weekly Status Meeting
[17:00] <ppisati> o/
[17:00] <cking> o/
[17:00] <herton> o/
[17:00] <henrix> o/
[17:00] <ogasawara> o/
[17:00] <smb> O/
[17:00] <sforshee> o/
[17:00] <jsalisbury> [TOPIC] ARM Status (ppisati)
[17:01] <ppisati> nothing new to report this week
[17:01] <ppisati> ..
[17:01] <jsalisbury> [TOPIC] Release Metrics and Incoming Bugs (jsalisbury)
[17:01] <jsalisbury> Release metrics and incoming bug data can be reviewed at the following link:
[17:01] <jsalisbury> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:01] <jsalisbury> ..
[17:01] <jsalisbury> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:01] <ogasawara> The Precise kernel is currently frozen and we are gearing up for release
[17:01] <ogasawara> this Thurs Apr 24.  Release candidate images are already available.  We
[17:01] <ogasawara> have prepared a day-0 kernel upload that contains a few bug fixes which
[17:01] <ogasawara> we would like to have immediately available to users.  We will upload the
[17:01] <ogasawara> day-0 kernel to precise-proposed today and it will be pocket copied to
[17:01] <ogasawara> precise-updates.  I then intend to hand the maintenance repsonibilities
[17:01] <ogasawara> of the Precise kernel over to the Stable Maintenance Kernel Team on
[17:01] <ogasawara> Friday.
[17:01] <ogasawara> Important upcoming dates:
[17:01] <ogasawara>  * Thurs Apr 26 - Final Release (2 days! \o/)
[17:01] <ogasawara> ..
[17:01] <jsalisbury> [TOPIC] Status: CVE's (apw)
[17:02] <apw> Currently we have 76 CVEs on our radar, with 5 new CVEs added this week.
[17:02] <apw> See the CVE matrix for the current list:
[17:02] <apw>  
[17:02] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/ALL-linux.html
[17:02] <apw>  
[17:02] <apw> Overall the backlog has increased slightly slightly this week:
[17:02] <apw>  
[17:02] <apw> [LINK] http://people.canonical.com/~kernel/status/cve-metrics.txt
[17:02] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:02] <apw>  
[17:02] <apw> This week sees the vestages of maverick dropping from the tracker.
[17:02] <apw>  
[17:02] <apw> ..
[17:02] <jsalisbury> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:02] <bjf>     
[17:02] <bjf> Here is the status for the main kernels, until today (Apr. 24):
[17:02] <bjf>  
[17:02] <bjf>  * Hardy    - 2.6.24-31.101 - Nothing last cycle
[17:02] <bjf>  * Lucid    - 2.6.32-41.88  - In updates
[17:02] <bjf>  * Natty    - 2.6.38-14.58  - In updates
[17:02] <bjf>  * Oneiric  - 3.0.0-19.32   - Regression testing
[17:02] <bjf>  
[17:02] <bjf> Current opened tracking bugs details:
[17:02] <bjf>  * http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[17:02] <bjf>  
[17:02] <bjf> For SRUs, SRU report is a good source of information:
[17:02] <bjf>  * http://people.canonical.com/~kernel/reports/sru-report.html
[17:02] <bjf>  
[17:02] <bjf> Future stable cadence cycles:
[17:02] <bjf>  * https://wiki.ubuntu.com/PrecisePangolin/ReleaseInterlock
[17:03] <bjf>     
[17:03] <bjf>         
[17:03] <bjf> Due to this being releas week and people get testy when we upload
[17:03] <bjf> a barrage of SRU kernels, we are starting the next cadence cycle
[17:03] <bjf> next week. This also works out conveniently making UDS week a
[17:03] <bjf> bug verification week.
[17:03] <bjf>     
[17:03] <bjf> ..
[17:03] <jsalisbury> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:03] <jsalisbury> Thanks everyone
[17:03] <jsalisbury> #endmeeting
[17:03] <meetingology> Meeting ended Tue Apr 24 17:03:56 2012 UTC.
[17:03] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-24-17.00.moin.txt
[17:03] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-04-24-17.00.html