2012-10-12
Size: 5280
Comment:
|
← Revision 128 as of 2012-10-12 11:11:55 ⇥
Size: 7451
Comment:
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was copied from ReleaseTeam/Meeting/2012-02-10 ## page was copied from ReleaseTeam/Meeting/2012-02-03 = 12.04 LTS (Precise Pangolin) Weekly Meeting = |
## page was copied from ReleaseTeam/Meeting/2012-10-05 = 12.10 (Quantal Quetzal) Weekly Meeting = |
Line 7: | Line 6: |
* 2012/02/16 - '''FeatureFreeze''' at 2100 UTC * 2012/02/16 - '''10.04.4''' * 2012/06/23 - '''UserInterfaceFreeze''' * 2012/06/23 - '''BetaFreeze''' at 2100 UTC * 2012/02/02 - '''Beta 1''' |
* '''12.10''' * October 16 - [[https://wiki.ubuntu.com/FinalFreeze|Unseeded Universe Final Freeze]] * October 18 - '''12.10 Release''' == Pending Actions == * none |
Line 15: | Line 16: |
* Work Items for 12.04: * There are now XXXX was 2895 on 2012/02/09) (2084 on 2011/11/25). * please review your blueprints for those work items its clear won't happen this release, and set them to POSTPONED. |
* Work Items for 12.10: 2752 on 10/12 was 2997 on 9/28 * 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 |
Line 19: | Line 22: |
* Precise Schedule: * see: https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule * google calendar: http://fridge.ubuntu.com/calendars/ubuntu-release-calendar/ |
* Quantal Schedule: * current: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule * google calendar: http://fridge.ubuntu.com/calendars/ubuntu-release-calendar |
Line 24: | Line 27: |
* '''Current list''': http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html * Reminder: if you want a team to find and consider a bug quickly, '''please assign or subscribe the bug to that team'''. |
* '''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 27: | Line 31: |
* 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 28: | Line 41: |
== Hardware Certification team update - mlegris == | * 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 == |
Line 32: | Line 60: |
== QA team update - jibel == * Alpha 2 test results: https://wiki.ubuntu.com/QATeam/ReleaseReports/PreciseAlpha2TestReport |
== QA team update - gema == |
Line 37: | Line 63: |
* Work items: http://status.ubuntu.com/ubuntu-precise/canonical-platform-qa.html | * Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-platform-qa.html * Upcoming tasks: https://launchpad.net/~canonical-platform-qa/+upcomingwork |
Line 40: | Line 67: |
* fresh ISO install: https://jenkins.qa.ubuntu.com/view/Precise%20Daily%20ISOs/ * upgrades: https://jenkins.qa.ubuntu.com/view/Precise/job/precise-upgrade/ |
* fresh ISO install: https://jenkins.qa.ubuntu.com/view/Quantal%20Daily%20ISOs/ * upgrades: https://jenkins.qa.ubuntu.com/view/Quantal/job/quantal-upgrade/ |
Line 43: | Line 70: |
== Community testing update - balloons == * see: * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-quality-community-testing.html |
|
Line 47: | Line 79: |
* Work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-security-essential.html | * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-security-essential.html * Upcoming tasks: https://launchpad.net/~canonical-security/+upcomingwork |
Line 52: | Line 85: |
* Work items: * http://status.ubuntu.com/ubuntu-precise/canonical-kernel-team.html * http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team-ubuntu-12.04-beta-1.html * http://status.ubuntu.com/ubuntu-precise/canonical-kernel-distro-team.html |
* Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team.html * Upcoming tasks: https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork |
Line 58: | Line 89: |
== Foundations team update - cjwatson == | == Foundations team update - ogra == |
Line 60: | Line 91: |
* see: * Work items:http://status.ubuntu.com/ubuntu-precise/canonical-foundations.html |
* see: * Work items:http://status.ubuntu.com/ubuntu-quantal/canonical-foundations.html * Upcoming tasks: https://launchpad.net/~canonical-foundations/+upcomingwork |
Line 66: | Line 97: |
* see: ? | * see: |
Line 68: | Line 99: |
* Infrastructure: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-servercloud-infrastructure-deployment.html * LTS hardening: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-servercloud-lts-hardening.html |
* 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 |
Line 72: | Line 103: |
* ARM server: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-servercloud-arm.html * Upcoming tasks: https://launchpad.net/~canonical-server/+upcomingwork |
|
Line 74: | Line 107: |
== ARM team update - ogra == * see: ? * Work items: http://status.ubuntu.com/ubuntu-precise/ubuntu-arm.html * Armhf - FTBFS - http://qa.ubuntuwire.org/ftbfs/primary-precise-armhf.html |
|
Line 82: | Line 110: |
* see: ? * Planning: https://launchpad.net/linaro-dev-platform/+milestone/11.12 |
* see: * Planning: https://launchpad.net/linaro-dev-platform/+milestone/12.07 |
Line 89: | Line 118: |
== Desktop Team update - pitti == | == Desktop Team update - seb128 == |
Line 91: | Line 120: |
* see: ? | * see: |
Line 93: | Line 122: |
* Work items: http://status.ubuntu.com/ubuntu-precise/canonical-desktop-team.html | * Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-desktop-team.html * Upcoming tasks: https://launchpad.net/~canonical-desktop-team/+upcomingwork |
Line 95: | Line 125: |
== Desktop Experience Team Update - dbarth == | == Unity Team update - popey == |
Line 97: | Line 127: |
* see: ? * Work items: (in progress, assessing bug workload) |
* see: * plans: ?? |
Line 100: | Line 130: |
== Desktop Systems Engineering Update - Cami == | == Kubuntu Team update - jr == |
Line 102: | Line 132: |
* see: ? * Work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-desktop-touch.html == Kubuntu Team update - Riddell == * see: ? * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-kubuntu.html |
* see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-kubuntu.html |
Line 112: | Line 137: |
* see: ? * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-edubuntu.html |
* see: * work items: http://status.ubuntu.com/ubuntu-quanatal/group/topic-quantal-flavor-edubuntu.html |
Line 115: | Line 140: |
== Xubuntu Team update - madnick == | == Xubuntu Team update - knome or astraljava == |
Line 117: | Line 142: |
* see: ? * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-xubuntu.html |
* see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-xubuntu.html |
Line 122: | Line 147: |
* see: ? * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-ubuntu-studio.html |
* see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntustudio.html |
Line 127: | Line 152: |
* see: ? * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-lubuntu.html |
* see: * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-lubuntu.html |
Line 132: | Line 157: |
* see: ? | * Working on 12.04.1 LTS, not 12.10 |
Line 134: | Line 159: |
== MOTU Team Q&A - tumbleweed or Laney == | |
Line 136: | Line 160: |
* ? | == MOTU Team Q&A - tumbleweed, iulian or Laney == |
Line 138: | Line 162: |
== 10.04.4 == * https://bugs.launchpad.net/ubuntu/lucid/+bugs?field.milestone%3Alist=30510 * http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-mgr-l-tracking-bugs.html |
* ? |
Line 149: | Line 170: |
## * Meetingology: http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-01-20-16.01.moin.txt ## * IRC log:http://irclogs.ubuntu.com/2011/12/09/%23ubuntu-meeting.html#t16:00 |
* Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-12-15.00.moin.txt * Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-12-15.00.html * IRC log: http://irclogs.ubuntu.com/2012/10/12/%23ubuntu-meeting.html#t15:00 |
12.10 (Quantal Quetzal) Weekly Meeting
Upcoming Dates
12.10
October 16 - Unseeded Universe Final Freeze
October 18 - 12.10 Release
Pending Actions
- none
Release Overview
- Work Items for 12.10: 2752 on 10/12 was 2997 on 9/28
- 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)