2012-10-12
1059
Comment:
|
7715
|
Deletions are marked like this. | Additions are marked like this. |
Line 2: | Line 2: |
= 12.04 = | = 12.10 (Quantal Quetzal) Weekly Meeting = |
Line 6: | Line 6: |
11/24 - Feature Planning Freeze 12/01 - Alpha 1 |
* '''12.10''' * October 9 - [[https://wiki.ubuntu.com/TranslationDeadline|Translation Deadline]], [[https://wiki.ubuntu.com/FinalFreeze|Seeded Images Final Freeze ]] * October 11 - [[https://wiki.ubuntu.com/ReleaseCandidate|Release Candidate]], and [[https://wiki.ubuntu.com/ReleaseNotesFreeze|Release Note Content Freeze]] * October 16 - [[https://wiki.ubuntu.com/FinalFreeze|Unseeded Universe Final Freeze]] * October 18 - '''12.10 Release''' |
Line 9: | Line 12: |
== Logisitics == | == Pending Actions == |
Line 11: | Line 14: |
* any round table order changes requested? | * none |
Line 13: | Line 16: |
* reminder - team statuses should be on ubuntu-release mail list at least 4 hours before the meeting. | == Release Overview == * Work Items for 12.10: 2997 on 9/28 was 2996 on 9/20 * 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''': * Consider to fix: http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-incoming-bug-tasks.html * Commit to fix: http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-tracking-bug-tasks.html |
Line 15: | Line 33: |
* Bug tracking workflow has now changed: * see: https://blueprints.launchpad.net/ubuntu/+spec/other-q-release-bug-list-workflows * stakeholders [[http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-incoming-bug-tasks.html|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 [[http://reports.qa.ubuntu.com/reports/rls-mgr/rls-q-notfixing-bug-tasks.html|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. |
|
Line 16: | Line 43: |
== Team Round Table == | * At '''start of meeting''', please wave or say hi so we know you're present and paying attention. |
Line 18: | Line 45: |
* '''DRAFT''' will solidify this a bit better for next weeks | * 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/'). |
Line 20: | Line 51: |
=== Hardware Certification team update - mlegris === | I'll try to call on folks in the order I see "o/"s showing up after the Q&C session starts. |
Line 22: | Line 53: |
=== QA team update - jibel === | 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. |
Line 24: | Line 55: |
=== Security team update - jdstrand or mdeslaur === | Suggestions on improving the above conventions are most welcome. |
Line 26: | Line 57: |
=== Kernel team update - ogasawara ==== | |
Line 28: | Line 58: |
=== Foundations team update - cjwatson === | == Hardware Certification team update - brendand == |
Line 30: | Line 60: |
=== Server team update - Daviey === | * see: |
Line 32: | Line 62: |
=== ARM team update - ogra === | == QA team update - gema == |
Line 34: | Line 64: |
=== Linaro update - fabo === | * see: * Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-platform-qa.html * Upcoming tasks: https://launchpad.net/~canonical-platform-qa/+upcomingwork |
Line 36: | Line 68: |
=== Ubuntu One Team - joshuahoover === | * Daily testing status can be found: * fresh ISO install: https://jenkins.qa.ubuntu.com/view/Quantal%20Daily%20ISOs/ * upgrades: https://jenkins.qa.ubuntu.com/view/Quantal/job/quantal-upgrade/ ## * to get test information pushed to you subscribe to: https://lists.ubuntu.com/mailman/listinfo/ubuntu-testing-notifications |
Line 38: | Line 73: |
=== Desktop Team update - pitti === | == Community testing update - balloons == |
Line 40: | Line 75: |
=== Desktop Experience Team Update - dbarth === | * see: * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-quality-community-testing.html |
Line 42: | Line 78: |
=== Kubuntu Team update - Riddell === | == Security team update - mdeslaur == |
Line 44: | Line 80: |
=== Edubuntu Team update - stgraber or highvoltage === | * see: * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-security-essential.html * Upcoming tasks: https://launchpad.net/~canonical-security/+upcomingwork |
Line 46: | Line 84: |
=== Xubuntu Team update - ??? === | == Kernel team update - ogasawara == |
Line 48: | Line 86: |
=== Lubuntu Team update - gilir === | * 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 |
Line 50: | Line 91: |
=== MOTU Team update - tumbleweed or Laney === | == 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.07 == 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: * plans: ?? == Kubuntu Team update - jr == * see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-kubuntu.html == Edubuntu Team update - stgraber or highvoltage == * see: * work items: http://status.ubuntu.com/ubuntu-quanatal/group/topic-quantal-flavor-edubuntu.html == Xubuntu Team update - knome or astraljava == * see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-xubuntu.html == Ubuntu Studio update - scott-work == * see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntustudio.html == Lubuntu Team update - gilir == * see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-lubuntu.html == Mythbuntu Team update - superm1 == * Working on 12.04.1 LTS, not 12.10 == MOTU Team Q&A - tumbleweed, iulian or Laney == * ? == Other Topics == * none = Q&A by the teams on the above status = * Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-28-15.00.moin.txt * Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-09-28-15.00.html * IRC log: http://irclogs.ubuntu.com/2012/09/28/%23ubuntu-meeting.html#t15:00 |
12.10 (Quantal Quetzal) Weekly Meeting
Upcoming Dates
12.10
October 9 - Translation Deadline, Seeded Images Final Freeze
October 11 - Release Candidate, and Release Note Content Freeze
October 16 - Unseeded Universe Final Freeze
October 18 - 12.10 Release
Pending Actions
- none
Release Overview
- Work Items for 12.10: 2997 on 9/28 was 2996 on 9/20
- 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:
Quantal:
- 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&C 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 - gema
- 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/group/topic-quantal-quality-community-testing.html
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.07
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:
- plans: ??
Kubuntu Team update - jr
Edubuntu Team update - stgraber or highvoltage
Xubuntu Team update - knome or astraljava
Ubuntu Studio update - scott-work
- see:
work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntustudio.html
Lubuntu Team update - gilir
Mythbuntu Team update - superm1
- Working on 12.04.1 LTS, not 12.10
MOTU Team Q&A - tumbleweed, iulian or Laney
- ?
Other Topics
- none
Q&A by the teams on the above status
ReleaseTeam/Meeting/2012-10-12 (last edited 2012-10-12 11:11:55 by 99-191-111-134)