2012-10-05
|
Size: 7292
Comment:
|
Size: 7675
Comment: add the pending actions from prior meetings.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
== Pending Actions == * summarize on ubuntu-release what desktop want for 12.04.1 (seb128, 201206 15:15:33:13) * 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 |
12.10 (Quantal Quetzal) Weekly Meeting
Upcoming Dates
2012/07/05 - DebianImportFreeze
- 2012/07/23 - Alpha 3 image candidates start
- 2012/07/26 - Alpha 3
Pending Actions
- summarize on ubuntu-release what desktop want for 12.04.1 (seb128, 201206 15:15:33:13)
- 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)
Release Overview
- 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:
- Bugs being tracked:
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'
Meeting Format
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.
Hardware Certification team update - brendand
- see:
QA team update - jibel
- see:
Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-platform-qa.html
Upcoming tasks: https://launchpad.net/~canonical-platform-qa/+upcomingwork
- Daily testing status can be found:
Community testing update - balloons
- see:
Work items: http://status.ubuntu.com/ubuntu-quantal/u/nskaggs.html
- Upcoming tasks:
Security team update - mdeslaur
- see:
Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-security-essential.html
Upcoming tasks: https://launchpad.net/~canonical-security/+upcomingwork
Kernel team update - ogasawara
- see:
Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team.html
Upcoming tasks: https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
Bugs: http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/_kernel_hot_.html
Foundations team update - ogra
- see:
Work items:http://status.ubuntu.com/ubuntu-quantal/canonical-foundations.html
Upcoming tasks: https://launchpad.net/~canonical-foundations/+upcomingwork
Server team update - arosales
- see:
- Work items:
Infrastructure: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-servercloud-infrastructure-deployment.html
LTS 12.04.1 hardening: http://status.ubuntu.com/ubuntu-precise/group/topic-quantal-servercloud-12.04.1.html
Juju charms and service orchestration: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-servercloud-service-orchestration.html
cloud workload: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-servercloud-workloads.html
ARM server: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-servercloud-arm.html
Upcoming tasks: https://launchpad.net/~canonical-server/+upcomingwork
Bugs: http://status.qa.ubuntu.com/reports/ubuntu-server/release-bugs.html
Linaro update - fabo
- see:
Planning: https://launchpad.net/linaro-dev-platform/+milestone/12.06
Ubuntu One Team - joshuahoover
- see:
Desktop Team update - seb128
- see:
Team status: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-desktop-team.html
Upcoming tasks: https://launchpad.net/~canonical-desktop-team/+upcomingwork
Unity Team update - popey
- see:
- Work items: ??
Kubuntu Team update - jr
Edubuntu Team update - stgraber or highvoltage
Xubuntu Team update - madnick or knome
Ubuntu Studio update - scott-work
- see:
work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntu-studio.html
Lubuntu Team update - gilir
Mythbuntu Team update - superm1
- see: ?
MOTU Team Q&A - tumbleweed, iulian or Laney
- ?
Other Topics
- none
Q&A by the teams on the above status
ReleaseTeam/Meeting/2012-10-05 (last edited 2012-10-05 11:33:33 by 99-191-111-134)