2012-06-29

12.10 (Quantal Quetzal) Weekly Meeting

summarize on ubuntu-release what desktop want for 12.04.1 (seb128, 201206 15:15:33:13)
- DONE: from weekly report reply: we will keep doing what we did for previous LTSes, and support the same set of images that for the release, including the DVD ones.
start off a blueprint for -r release for people to record ideas and thoughts on logical steps for making progress to the long term goal. (skaet, 20120622 16:25:27)
- DONE: https://blueprints.launchpad.net/ubuntu/+spec/other-r-future-release-brainstorming

Work Items for 12.10:
- On blueprints, please remember to put all work items in the separate section, give it an importance and target blueprint to a specific milestone.
- All blueprints must be marked approved and targeted for the release to show up on the tracker.
- All blueprints must be marked approved and milestoned to show up on the +upcomingwork
- Suggested format to use for blueprints that are for feature development is: BlueprintSpec
Quantal Schedule:
- current: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule
- google calendar: http://fridge.ubuntu.com/calendars/ubuntu-release-calendar
Bugs being tracked:
- Quantal: http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-tracking-bug-tasks.html
- 12.04.1: http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html
Bug tracking workflow has now changed: see: https://blueprints.launchpad.net/ubuntu/+spec/other-q-release-bug-list-workflows
- stakeholders nominate bugs for Ubuntu Engineering by marking them with the 'rls-q-incoming' tag (where 'q' is the current release letter)
- engineering managers and/or defect analysts accept bugs from this incoming queue by targetting them to the quantal release and removing the rls-q-incoming tag
- engineering managers and/or defect analysts decline to commit to fix bugs by tagging them 'rls-q-notfixing'

To make this meeting efficient for everyone (and hopefully reduce confusion), would appreciate it if everyone tried to follow these conventions.

At start of meeting, please wave or say hi so we know you're present and paying attention.
Once the topic, becomes Question and Answer Session,
- When you have a new question to ask, or thread of conversation to start off, please raise your hand "o/"
- If your just asking a follow up question/commenting on the current open question - just type.
- When possible, please target your questions to specific individuals by using their nick. Others should feel free to comment if they have information to add to the discussion.
- When you've finished your comments on the current question/discussion topic, please use the convention ".." so we know you're done, and we can move on to the next queue'd up question (as indicated by a 'o/').

I'll try to call on folks in the order I see "o/"s showing up after the Q&A session starts.

Once there are no more "o/"'s in the queue, we'll end the meeting, there won't be an any other business topic, etc.

Suggestions on improving the above conventions are most welcome.