Server Team 20100303 meeting minutes

[Thierry Carrez]

Hi,

Here are the minutes of meeting. They can also be found online with the 
irc logs here: https://wiki.ubuntu.com/MeetingLogs/Server/20100303.


==== Review ACTION points from previous meeting ====

  * kirkland to publish tentative bugzapping roadmap: Done, will be updated.

==== Beta1 status review ====

ttx informed everyone that we are at the beginning of the beta1 
subcycle... but not very far from the end of it. Thursday next week is 
Beta1Freeze, a hard freeze before the Beta1 release, so most uploads 
should be made before that date. For reference, the beta1-targeted 
blueprints are tracked at [1].

smoser reported that the EBS root support was on track, with all tools 
moved over to using the new api tools.

[1] 
http://people.canonical.com/~pitti/workitems/canonical-server-ubuntu-10.04-beta-1.html

==== Weekly Updates & Questions for the QA Team (hggdh) ====

hggdh reported that the build in MySQL regression PPA was still failing, 
and zul confirmed that he was working on it. hggdh didn't have the time 
to look into the UEC test rig yet, but will do this week (the idea being 
that he should be able to run the post-A3, pre-beta1 UEC tests). hggdh 
also reported good progress on mastering the automated ISO testing 
framework soren was previously working on.

==== Weekly Updates & Questions for the Kernel Team (jjohansen) ====

jjohansen reported bug 527208 outstanding, blocking boot on c1.xlarge 
type instances in EC2: it should hopefully be fixed this week. mathiaz 
brought his request for creating vlan modules for d-i (bug 530459) to 
the kernel team attention.

==== Server Papercuts (ttx) ====

14 bugs[2] were targeted for the first papercuts fixing campaign, which 
will end on Beta1Freeze, Thursday next week. Everyone is welcome to 
assign themselves some of those bugs, which are usually easy to fix. 
ScottK offered support in helping fixing the amavisd-new bugs.

There is still some room in the second campaign (beta2), so people 
should keep on nominating their favorite annoyance as a bug also 
affecting the "Server papercuts" project. In the nomination list, bug 
211915 was accepted and assigned to sommer for the beta2 campaign.

[2] https://launchpad.net/server-papercuts/+milestone/lucid-beta-1

==== Bugzapping (kirkland) ====

kirkland reported good progress on the current kvm bugzapping effort, 
and now Lucid's kvm package appears to be in good shape. He might not 
have time to get around to libvirt, where there's a lot more open bugs, 
due to other pressing work. A eucalyptus bugzapping week is also already 
planned. Other bugzapping efforts will have to be organized by other people.

In order to encourage that, the bugzapping format will be slightly 
simplified to lower the barrier of entry: you should target as a group a 
single package and spend a minimum of 2 days on it (Triaging / 
Bugfixing), ideally 3 days. People interested in chairing such an effort 
should edit the ServerLucidBugZapping wikipage[3].

kirkland also mentioned that bugzapping was a great way for community 
members in companies that care about the shape of a particular package 
to get involved: you should consider asking your boss/work for 2-3 days 
to focus on Ubuntu XYZ package where XYZ is the key package that your 
company/business/IT-staff needs working better in Ubuntu.

On a related front, ScottK reported that someone should figure out why 
suddenly tons of people who have no idea how to configure postfix are 
installing it, which he traced back to some Google Chrome packages.

[3] https://wiki.ubuntu.com/ServerLucidBugZapping

==== Update on Daily Bug triager: New,Undecided bugs (mathiaz) ====

mathiaz updated the daily query to be live ("New Bugs" link at [4]). He 
wanted to remind everyone to triage all bugs on the list on their Triage 
day: starting at the top and processing one bug after the other at least 
until you reach one opened on today.

[4] https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#triager

==== Open Discussion ====

Daviey asked if, as part of the ArchiveReorg that is being phased in, 
people should think about requesting ubuntu-server upload privileges. 
The team details need to be sorted out first, and we didn't feel the 
urgency of it since most interested people are already core-dev. However 
in order to lower the barrier of entry, it makes sense to set the team 
in place in all cases.

jmdault mentioned upcoming updates to Asterisk, due to two recent 
security fixes.

ACTION:  mathiaz to sync up with cjwatson re: ubuntu-server upload team

==== Announce next meeting date and time ====

Next meeting will be on Wednesday, March 10th at 14:00 UTC in 
#ubuntu-meeting.

-- 
Thierry Carrez
Ubuntu server team