Ubuntu News
Here are the minutes of the meeting. They can also be found online
with the irc logs here.
Review ACTION points from previous meeting (jib)
- ACTION: ttx to announce papercuts nominations
- ACTION: zul to do another call to action for the apport hooks involvement
- ACTION: zul to raise php5.3 update on -server and -devel mailinglist, outline which apps are currently not working with 5.3
Alpha3 progress review (ttx)
- Make sure status is updated on each of your blueprint whiteboards EOD on Tuesdays !
-
Prio 1 specs < 70% completed: uec-testing, mysql-5.0, seeds
- uec-testing (mathiaz)
- kirkland: testing iso’s today
- mathiaz: good shape
- mysql-5.0 (zul)
- [ACTION] zul to forward issues about ctbd to jelmer to see if those can be lifted before FF
- [ACTION] zul to do another call to action for the apport hooks involvement
- Discussion on RHCS, whether to keep in main, move to universe; mailing list thread should reach a conclusion soon
- daily-vcs (zul)
- zul: been working on higher priority specs
- puppet-etckeeper-integration (mathiaz, soren)
- soren, mathiaz: should merge from debian unstable, not in danger
-
Prio 2 specs < 50% completed: daily-vcs, puppet-etckeeper-integration, puppet-uec-ec2-integration
server-lucid-papercuts (ttx)
server-lucid-papercuts
server-lucid-apport-hooks update (zul)
server-lucid-apport-hooks
Weekly Updates & Questions for the QA Team (soren)
- smoser: new guy starts: 15th (which is a US holiday) so 16th
- soren: handed over automatic ISO testing stuff to the QA team. It’ll be running in the DC soon.
Weekly Updates & Questions for the Kernel Team (jjohansen)
- jjohansen: new EC2 kernel is checked in, has the latest updates, and updated configs
Weekly SRU review (mathiaz)
Open Discussion
- kirkland: tftpd-hpa in lucid sucks
- stgraber: I’m still not sure about what to do here but I’m very tempted to restore the old behavior
- ttx: Ubuntu bug 508382 in bacula “bconsole does not connect to bacula-director” [Medium,Confirmed]
Agree on next meeting date and time
- ttx: That will be again same place same time, for at least one more week
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* Pitivi!
* #16 New bugs need a hug
* #8 Incomplete bugs need a status check
* #8 Confirmed bugs need a review
* #1 Bug to be forwarded Upstream
Pitivi is a video editor that is being included by default in the next
version of Ubuntu (Lucid Lynx). So its very important that we hug some
bugs in preparation. Issues that you should look out for is older bugs
that dont effect the current version.
Bookmark it, add it to your calendars, turn over those egg-timers!
* February 11th
* https://wiki.ubuntu.com/UbuntuBugDay/20100211
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project?
Did you ever wonder what Triage is? Want to learn about that?
This is a perfect time!, Everybody can help in a Bug Day!
open your IRC Client and go to #ubuntu-bugs (FreeNode)
the BugSquad will be happy to help you to start contributing!
Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
work your name could be listed at the top 5-A-Day Contributors in the
Ubuntu Hall of Fame page!
We are always looking for new tasks or ideas for the Bug Days, if you
have one
add it to the Planning page
https://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this, head to
http://wiki.ubuntu.com/Bugs
Do you have a nVIDIA or ATI graphics card? Do you want to help ensure users have a smooth experience if they choose to use the proprietary drivers?
We are looking for committed volunteers to test nVIDIA and ATI proprietary drivers on a weekly basis. The goal of this testing is to catch regressions early in the cycle, and fix bugs before they reach a major audience.
If you want to be part of the team you will need:
- A computer with an ATI (R600 or newer) or nVIDIA (GeForce series 2 or newer) graphics card
- A spare partition on that system
- If you don't have a spare partition you can easily create one
- One hour of your time per week
- An Internet connection
If you want to take part in this adventure, please, send me an email (ara AT ubuntu DOT com) with the exact model of your graphics card , and I will get back to you with detailed instructions.
Thanks for helping making Ubuntu even better!
P.S. This project is to test the proprietary drivers. If you're interested in testing the free drivers, we don't need installation testing but help is always welcome. Check how you can help at the Ubuntu X team page.
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* ubuntuone-client!
* 115 New bugs need a hug
* 148 Incompletes bugs
* 34 Confirmed bugs need a review
Bookmark it, add it to your calendars, turn over those egg-timers!
* Thursday 28 January 2010
* https://wiki.ubuntu.com/UbuntuBugDay/20100128
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project? Did you ever wonder what Triage is? Want to
learn about that? This is a perfect time!, Everybody can help in a Bug Day!
Open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad
will be happy to help you to start contributing!
Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
work your name could be listed at the top 5-A-Day Contributors in the
Ubuntu Hall of Fame page!
We are always looking for new tasks or ideas for the Bug Days, if you have one
add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this and you want to know
more about ubuntu?, head to http://wiki.ubuntu.com/Bugs
Last week the Lucid Alpha3 development phase started. So in following our Alpha2 announcement below is what’s on the horizon for Alpha3. Some of these are new blueprints for Alpha3 some are continued work from Alpha2.
Alpha3 Projects
Since the upcoming release is an LTS, a lot of this cycles work is centered around stability. Currently, we’re broadly targeting the following 3 areas:
Software integration
Improving our UEC & EC2 experience
QA & testing
There are also a few community driven specs which are targeted for the Lucid release:
The full list of blueprints related to these targets and our progress can be found on the server team wiki or on our work item tracker.
Feedback & Involvement
If you have any suggestions for AWS libraries in PHP/Perl/Python or are interested in packaging/contributing a library in another language, please let us know in the RFC thread
To make the most of our Server Papercuts project, please participate in the email discussion and nominate papercuts and/or volunteer to fix them!
To help us track down bugs and crashes better, we’re adding apport hooks to several key pieces of software. If you’d like to implement any of those hooks or contribute your own, please let us know in
the blueprint.
The Ubuntu Cluster Stack spec has issued a call for testing and would love to hear about your experiences.
Here are the minutes of the meeting. They can also be found online
with the irc logs here.
Review ACTION points from previous meeting
- smoser to look at getting Karmic images refreshed: bug verifiedfixed, image refresh coming up before end of week
Action: smoser to publish karmic cloud image refresh
Spec quickreview
All alpha-3 targeted specs are on track.
To avoid useless noise, blueprint assignees are asked to refresh the status of their specs by using the “Status:” section of the blueprint whiteboard. It will then automagically show up in the report (http://people.canonical.com/~pitti/workitems/canonical-server-lucid-alpha-3.html).
Action: Everyone: update status for your specs before the meeting starts
Alpha3 subcycle planning
The final planning is still being discussed, and should be officialized this week. No change is expected in the Prio 1 specs (“High” priority), some priority changes might affect Prio2/3 specs, and some late specs might be introduced as Prio2/3 specs.
server-lucid-papercuts
We discussed the papercuts acceptance criteria, as described in a recent ubuntu-server ML post. This looks fine and was approved. Final criteria should make clear that any server-related package (in main, universe or multiverse) is relevant, and that the fix should not introduce a new feature (and therefore be OK to fix after FeatureFreeze). The criteria might be further refined when we start hitting difficult nominations.
About the project publicity plan, mathiaz already posted a blog entry about the project on the ubuntuserver blog. This should be complemented by an ubuntu-devel ML post, personal blog posts (ttx, zul) and brought to the attention of the Ubuntu Weekly News team. alexm will talk about it in his loco. The message is about nominating your favorite server papercuts, so that we gather as many candidates as possible now.
Action: ttx, zul to blog about papercuts, make sure UWN gets the word
Action: ttx to send email about criteria and nomination to ubuntu-devel, ubuntu-server
server-lucid-apport-hooks
Building on the UDS Dallas discussion about how having apport hooks in server packages can help the quality of the bug reports we receive, the server apport hooks effort aims at adding as many as we can before FeatureFreeze. zul created a page at https://wiki.ubuntu.com/ServerTeam/ApportHooks with likely candidates. Anyone interested, please sign up for your favorite package, or add your own !
Weekly Updates & Questions for the QA Team
soren has been extending the ISO testing features, and can now at the click of a button run ISO tests of the cartesian product of i386/amd64,lvm/non-lvm,basic/mail/bind9/lamp/postgresql installs. Documentation on the setup is under way, and the process should be ultimately integrated with Marc Tardif’s checkbox work. soren will lead an UbuntuDeveloperWeek session about this next Tuesday at 2000 UTC.
Weekly Updates & Questions for the Kernel Team
Discussion concentrated on bug 494565, since a decision must be reached on the best option to follow. The -virtual kernel currently being a subflavour of -server and -generic-pae, building support for the block devices needed for EC2 and UEC would also affect those kernels. The options are CONFIG_SCSI_SYM53C8XX_2, CONFIG_VIRTIO_NET and CONFIG_VIRTIO_BLK. CONFIG_SCSI_SYM53C8XX_2=y, in particular, could have unexpected consequences on some rare hardware. Note that building in that SCSI support would not prevent it from being manually bypassed. Alternatives would be to make -virtual a flavour of its own (but this adds a lot of maintenance work for the kernel team), patch UEC so that it works without that SCSI support (potential performance issues, deviation from upstream), or abandon the idea of using no ramdisks for UEC. This should be further discussed on ubuntu-devel.
Action: smoser to raise thread about the no-ramdisk / -virtual config tradeoff
Assigned and to-be-assigned bugs
List at http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html still needs to be cleaned up to be more useful.
Action: zul, kirkland to unassign themselves from “maybe working on one day” bugs
Agree on next meeting date and time
Next meeting will be on Wednesday, January 27th at 14:00 UTC in #ubuntu-meeting.
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* network-manager-applet!
* 100 New bugs need a hug
* 26 Incompletes bugs
* 40 Confirmed bugs need a review
* 6 Bugs needs to be forwarded
Bookmark it, add it to your calendars, turn over those egg-timers!
* Thursday 21 January 2010
* https://wiki.ubuntu.com/UbuntuBugDay/20100121
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project? Did you ever wonder what Triage is? Want to
learn about that? This is a perfect time!, Everybody can help in a Bug Day!
Open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad
will be happy to help you to start contributing!
Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
work your name could be listed at the top 5-A-Day Contributors in the
Ubuntu Hall of Fame page!
We are always looking for new tasks or ideas for the Bug Days, if you have one
add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this (like me!) and you want to know
more about ubuntu?, head to http://wiki.ubuntu.com/Bugs
At UDS Lucid in Dallas the Ubuntu Server team had a session on how to take the opportunity of the LTS release to concentrate on fixing highly-annoying, low-hanging fruit bugs. This effort lead by Thierry Carrez was named Server papercuts as a tribute to the famous One hundred papercuts project from the Desktop experience team.
The idea is to spend time during this less-featureful development cycle to fix server usability issues to make Ubuntu Server even more sysadmin-friendly. The first part of this work involves identifying such issues, and for that we need the help of the Ubuntu Server user community, which experiences those issues every day. The second part is about fixing these Server papercuts. This is a great way to start being involved in bug fixing and Ubuntu development since these low hanging fruit should all be relatively easy-to-fix bugs.
How can I help?
If you come a across a bug in a server related package that looks like a good candidate, open a task against the server papercut project. The Ubuntu Server team will then review the different nomination and accept bugs that can be considered as low-hanging fruits.
If you have a patch to fix a bug, grab it and attach it to the bug. Or better, prepare a bzr branch and submit a merge proposal: the Ubuntu Server team will review it and guide you in the process of making your fix available in the archive.
The big number of Ubuntu bugs can sometimes be overwhelming. Providing high quality bugs can help in getting the bugs triaged and fixed faster. This is where Apport comes into the game – a tool used to automatically generate crash reports for debugging. Apport can be extended via hooks to provide specific information on a per package basis. For example the Ubuntu Server team added hooks for MySQL during the Karmic release cycle. Relevant logs as well as configuration information are automatically added to every bug reported against the mysql package.
If you have ideas about adding apport hooks for other server related packages let the Ubuntu Server team know. Add it to the wiki page, look up how to write apport hooks and prepare a patch – or better a bzr branch. The Ubuntu Server team will review it and help you integrate your work into the archive.
The second alpha for lucid is released. Download from the mirrors to enjoy the developer-y goodness and help in preparation for the lucid release.
The Ubuntu Server team is looking for feedback on which AWS client libraries should be made available as part of Ubuntu. Making it easy to develop applications that use AWS and UEC services is one of the goal of the Ubuntu Server team. The AWS client libraries blueprint focuses on listing existing projects and then choose which ones should be packaged for Lucid.
If you know of great projects in PHP, Perl, Python, Ruby, Java (or any other platform) that help using AWS and UEC services such as EC2 or S3 make a note of them in the wiki page (preferred choice) or by leaving a comment below.
While preparing for the second milestone on the road the Lucid Lynx release, the Ubuntu Server team is looking for help in testing the Ubuntu Server isos and EC2/UEC images. If you have some spare server hardware and have some time to dive into a RAID or LVM installation, head to the ISO QA tracker and pick one of the remaining ISO test cases.
If you’re more interested in the Cloud, either on EC2 or UEC, Lucid alpha2 candidates are available for testing as well. Bundle, run, test one of the image – and don’t forget to report your results to the ISO QA Tracker.
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* gnome-power-manager!
* 100 New bugs need a hug
* 100 Incompletes bugs
* 65 Confirmed bugs need a review
* 12 Bugs needs to be forwarded
Bookmark it, add it to your calendars, turn over those egg-timers!
* Thursday 14 January 2010
* https://wiki.ubuntu.com/UbuntuBugDay/20100114
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project? Did you ever wonder what Triage is? Want to
learn about that?
This is a perfect time!, Everybody can help in a Bug Day!
Open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad
will be happy to help you to start contributing!
Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
work your name could be listed at the top 5-A-Day Contributors in the
Ubuntu Hall of Fame page!
We are always looking for new tasks or ideas for the Bug Days, if you have one
add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this and you want to know
more about ubuntu?, head to http://wiki.ubuntu.com/Bugs
Here are the minutes of the meeting. They can also be found online
with the irc logs here.
Review ACTION points from previous meeting
Most of the assignee were not attending the meeting.
ACTION: jib to talk to robbiew about ecryptfs in ubuntu
Check blueprint status and progress for the week
- server-lucid-eucalyptus-karmic-retrospective: on track
- server-lucid-eucalyptus-merging-and-packaging: on track
- server-lucid-seeds: on track
- mathiaz is preparing the final list of packages and will ask for feedback on the remaining items.
- server-lucid-euca-remote-autoregister: 50% done, slightly slowed down by 1.6.2 integration work, on track
- server-lucid-uec-testing: on track, even though the completion rate is low.
Weekly Updates & Questions for the Kernel Team (jjohansen)
ttx brought bug 499785 – nic-usb-modules should include asix to the attention of the kernel team as it is needed to help test UEC in laptops environments.
mathiaz mentioned he had asked the kernel team for feedback on dropping the kernel-package package to universe.
Blueprints for post alpha2
Once alpha2 is out, the server team will look at the next set of blueprints to be implemented. Some of them still need more discussion which will happen during the next meeting on January 6th.
The following blueprints will be reviewed:
Agree on next meeting date and time
Next meeting will be on Wednesday, January 6th at 14:00 UTC in #ubuntu-meeting.
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* Bugs without a package!
* 100 New bugs need a hug and to be reassigned
* 100 Confirmed bugs need a review and also be reassigned
Bookmark it, add it to your calendars, turn over those egg-timers!
* Thursday 17 December 2009
* https://wiki.ubuntu.com/UbuntuBugDay/20091217
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project?
Did you ever wonder what Triage is? Want to learn about that?
This is a perfect time!, Everybody can help in a Bug Day!
open your IRC Client and go to #ubuntu-bugs (FreeNode)
the BugSquad will be happy to help you to start contributing!
Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
work your name could be listed at the top 5-A-Day Contributors in the
Ubuntu Hall of Fame page!
We are always looking for new tasks or ideas for the Bug Days, if you have one
add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this (like me!), you want receive a nice present
from santa and you want to know more about
ubuntu?, head to
http://wiki.ubuntu.com/Bugs
The Lynx is on the prowl – the first testing milestone of Lucid Lynx is released. Please see the announcement for details and download links.
Here are the minutes of the meeting. They can also be found online
with the irc logs here.
Scribe assignment
In an effort to share the burden, the responsibility and the community visibility, the meeting minutes scribe role will rotate alphabetically every week between the server team engineers. ttx will write up the current minutes, and zul will write the ones for next week. The process to follow is detailed in the Server team knowledge base. mathiaz can give access to the ubuntuserver blog to those missing it.
Review ACTION points from previous meeting
- jos to find out the best time for the meeting: Server meeting time to stay the same for at least the next month or two
Check blueprint status and progress for the week
Everything is green so far. The Alpha2 burn down chart is positive. ScottK mentioned that his mail integration spec still needs approval.
ACTION: jos to review/approve server-lucid-more-mail-integration
Alpha1 ISO testing
Lucid Alpha 1 candidates are now up on the ISO tracker. Everyone is encouraged to participate in testing them ! Cloud images should be up soon as well.
ACTION: smoser to push cloud dailies to ISO tracker asap
Assigned and to-be-assigned bugs
Nothing assigned to team needing re-assignment. Some team members are still assigned to more bugs than they should be actively working on, so this might need more review. No red flag raised.
Weekly Updates & Questions for the Kernel Team
KSM has been turned on and should land in post-Alpha1 kernels. It requires user space to use the madise system call to mark pages for sharing. That’s expected to be part of soon-released qemu-kvm 0.12. jjohansen still has to go through and update the EC2 configs to be more like virtual. On the table is also ramdisk-less images, -virtual kernels with all reasonable disk drivers for root devices as built-in, and Hz. This will be tracked in a bug that smoser will open.
ACTION: smoser to open bug for kernel team follow-up
Development sponsorship
Every server engineer with sponsorship capabilities is expected to spend one hour a week sponsoring stuff. The easiest way to track that is to do it every week at a fixed time, and combine it with Code reviews.
ACTION: zul, kirkland, mathiaz to sign up for sponsoring time on https://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews
Developer communication
Developer communication rules have been recently updated, please have a look at them and do the right thing.
soren’s QA project for Alpha2
Until Alpha-2, soren will be in the QA team, rather than the server team, working on automating a lot of the testing we are doing for servers. So far he has enabled a few test suites in package builds and set up kvm-autotest to do scripted, interactive testing.
Open Discussion
Instead of rewriting all Ubuntu Server python code in Perl, we plan to rewrite Jos in Python. Daviey encourages everyone to submit their Ubuntu Server tips to https://wiki.ubuntu.com/server-tips.
Agree on next meeting date and time
Next meeting will be on Wednesday, December 16th at 14:00 UTC in #ubuntu-meeting.
Announcing the Next Ubuntu Bug Day! - Thursday 10 December 2009
Fellow Ubuntu Triagers!
This week's Bug Day target is *drum roll please* Compiz!
* 120 New bugs need a hug
* 112 Incomplete bugs need a status check
* 61 Confirmed bugs need a review
* 2 bugs that need forward to upstream
Bookmark it, add it to your calendars, turn over those egg-timers!
* Thursday 10 December 2009
* https://wiki.ubuntu.com/UbuntuBugDay/20091210
Are you looking for a way to start giving some love back to your
adorable Ubuntu Project?
Did you ever wonder what Triage is? Want to learn about that?
This is a perfect time!, Everybody can help in a Bug Day!
open your IRC Client and go to #ubuntu-bugs (FreeNode)
the BugSquad will be happy to help you to start contributing!
Wanna be famous? Is easy! remember to use 5-A-day so if you do a good
work your name could be listed at the top 5-A-Day Contributors in the
Ubuntu Hall of Fame page!
We are always looking for new tasks or ideas for the Bug Days, if you have one
add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning
If you're new to all this and you want to know more about
ubuntu?, head to
http://wiki.ubuntu.com/Bugs
Lucid alpha 1 is due this Thursday, so the soft freeze is now in effect for main. Please be considerate with your uploads, and watch for any release blocker bugs.
 |
|
|
|
