Review Action Points from Previous Meeting
The actions were assigned at the previous meeting:
Action: smoser to publish karmic cloud image refresh (done) Action: Everyone: update status for your specs before the meeting starts (few left to do) Action: ttx, zul to blog about papercuts, make sure UWN gets the word (done) Action: ttx to send email about criteria and nomination to ubuntu-devel, ubuntu-server Action: smoser to raise thread about the no-ramdisk / -virtual config tradeoff (done) Action: zul, kirkland to unassign themselves from “maybe working on one day” bugs (done)
Alpha3 subcycle planning
Everything that’s marked ‘medium’ or high is fairly sure to make it into ‘alpha3′. ‘Low’ priority specs are targets of opprotunities and we’ll do our best to get as many of those done as possible. Please note there’s not been much change on this week but we pretty much expect it to be stable now.
No questions were raised in the discussion
A general status review was performed for specifications that were considered to be a “high” priority that are < 30%. The specifciations that were reviewed were:
jib raised the point that if you have anything you need f2f time with the team or others on the platform team, make sure your code’s in a shape to get cracking staight away on monday.
Now that project has been announced, we have 4 external papercut members, and 18 nominations so far. The next step is to discuss measurable objectives on how we should approach the papercuts. After much discussion, Thierry proposed that we review the papercuts proposals in the next meeting. It should be quick +1 round.
ACTION: ttx to announce papercuts nominations
zul provided an update on the current status and the next steps. zul mentioned that the php5 apport hook is complete, and the eucalyptus apport hook has been updated. However, there has not been any community contributions yet.
ACTION: zul to do another call to action for the apport hooks involvement
PHP 5.3 for Luicd
zul brought up in the meeting that Debian is moving to php version 5.3.1 for Debian Stable. It is currently in experimental and in the process to moving to Debian Unstable. zul mentioned that his preference is to stay with 5.2 since PHP applications that we care about (such as media wiki and drupal 5 still dont support PHP 5.3). Daivey asked if I have thought about what to with the “short tag” depreciation and mentioned that upstream is shipping with it by default. After much discussion about security, what it breaks, and to have it in backports the idea was to send an email to ubuntu-devel to get a wider variety of opinnons.
ACTION: zul to raise php5.3 update on -server and -devel mailinglist, outline which apps are currently not working with 5.3
Weekly Updates & Questions for the QA Team
Soren had perfrormed a UDW class on server automation which was great! Soren also mentioned that the PPA builds have been moved to a team PPA, so more people are being notified of build failures. He is also working on getting more of the qa-regression-testing run on a daily basis. As well as automated ISO testing will be moved to the DC
No other questions were raised for Soren.
Weekly Updates & Questions for the Kernel Team
A summary of launchpad bug 494565 was done by jjohansen. Jjohansen mentioned that the kernel team has changed the suggest configs to builtin (virto, virtnet, and 1 scsi). It booted in limited testing. Test images are available or you could have wait for the next kernel upload, (which is expected to be on friday). There is some concern that configs change will change the behavior so we need wider testing. It was noted that these changes were reasonably risk free but there is still some concern.
Assigned and to-be-assigned bugs
were cleaned up by kirkland and zul.
However there are new bugs there that has to be confirmed and triaged.
Weekly SRU review
The following bugs were nominated: #462172, #480152, #502878, #500457, #504897
Nothing was raised in the open discussion.
Agree on next meeting date and time
Next meeting will be on Tuesday, Feb 11 at 14:00 UTC in #ubuntu-meeting.
Recently at UDS in Dallas, the Ubuntu Server Team had a suggestion about little annoying things that users wanted fixed. Taking a page from the desktop this turned into the Ubuntu Server Papercuts project.
So the things that we are focusing on for the project are the small little things. Things like:
- Cron Job spamming root
- Low hanging fruit
- Minor annoyances for the sysadmin that keep them up at night
Remember the bug should be easily fixable, things like implement ipv6 for foo is obviously not a papercut. To nominate a bug for the papercuts project the process is the following:
- If the papercut isn’t already filed as an Ubuntu bug in Launchpad, go here.
- Look up the bug you want to nominate as a Server papercut, then click on “Also affects project”.
- Click “Choose another project” and type in “server-papercuts”, click “Continue”.
- Click on “Add to Bug report”.
When the bug list starts to fill up we will go through it and review them. But remember (from wikipedia):
A drop of ‘liquid bandage‘ or equivalent onto a paper cut can seal the skin to stop pain as well as prevent further opening of the wound (as is common on a location such as a finger).
In an effort to improve the quality of our bug reports it was decided at UDS in Dallas to take advantage of apport hooks.
At the session we had a list of packages that we want to add apport hooks for. The initial list that we came up was the following:
Now these are a lot of packages for that we need to write apport hooks for so I am asking the community in general to help out adding apport hooks. Also if you want to add more packages that you think should apport hooks please feel free! If you want to look at the specification, it can be found at here.
To contribute please open a bug in launchpad for the package with attached debdiff. I really appreciate the help and the ubuntu server community at large will also appreciate it.