2012-10-12

Differences between revisions 43 and 127 (spanning 84 versions)
Revision 43 as of 2012-02-10 03:11:21
Size: 5635
Editor: 99-191-111-134
Comment:
Revision 127 as of 2012-10-12 09:47:07
Size: 7769
Editor: 99-191-111-134
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## 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 6: Line 6:
 * 2012/02/16 - '''Feature Freeze''' 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 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'''

== Pending Actions ==

 * none
Line 14: Line 18:
 * Work Items for 12.04:
   * There are now 2907 (2012/02/02) up from 2876(2012/01/20) (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: 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
Line 18: Line 24:
 * 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 23: Line 29:
   * '''Committed for fixing''': 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'''.
   * Of interest to release: http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-mgr-p-tracking-bugs.html
   * '''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
 
 * 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.

 * 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.
Line 28: Line 58:
== Meeting Logistics == == Hardware Certification team update - brendand ==
Line 30: Line 60:
 * No IRC meeting on 2/3, day after milestone release.
   * Team summaries should still be mailed to ubuntu-release on Thurs or Friday
   * If urgent items, ad hoc meeting will be called on Monday.
 
  * see:
Line 35: Line 62:
== Hardware Certification team update - mlegris == == QA team update -  gema ==
Line 37: Line 64:
  * see: TBD

== QA team update - jibel ==

  * Alpha 2 test results: https://wiki.ubuntu.com/QATeam/ReleaseReports/PreciseAlpha2TestReport

  * see: TBD
  * Work items: http://status.ubuntu.com/ubuntu-precise/canonical-platform-qa.html
  * see:
  * Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-platform-qa.html
  * Upcoming tasks: https://launchpad.net/~canonical-platform-qa/+upcomingwork
Line 47: Line 69:
    * 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 50: Line 72:

== Community testing update - balloons ==

 * see:
 * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-quality-community-testing.html
Line 53: Line 80:
  * see: TBD
  * Work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-security-essential.html
  * see:
  * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-security-essential.html
  * Upcoming tasks: https://launchpad.net/~canonical-security/+upcomingwork
Line 58: Line 86:
  * see: https://lists.ubuntu.com/archives/ubuntu-release/2012-February/000783.html
  * Work items: http://status.ubuntu.com/ubuntu-precise/canonical-kernel-team.html
  * see:
  * Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team.html
  * Upcoming tasks: https://launchpad.net/~canonical-kernel-distro-team/+upcomingwork
Line 62: Line 91:
== Foundations team update - cjwatson == == Foundations team update - ogra ==
Line 64: Line 93:
  * 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 69: Line 99:
  * see: ?   * see:
Line 71: Line 101:
    * 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 75: Line 105:
    * ARM server: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-servercloud-arm.html
  * Upcoming tasks: https://launchpad.net/~canonical-server/+upcomingwork
Line 77: Line 109:
== 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 85: Line 112:
  * see: https://lists.ubuntu.com/archives/ubuntu-release/2012-February/000782.html
  * Planning: https://launchpad.net/linaro-dev-platform/+milestone/11.12
  * see:
  * Planning: https://launchpad.net/linaro-dev-platform/+milestone/12.07
Line 90: Line 118:
  * see: https://lists.ubuntu.com/archives/ubuntu-release/2012-February/000787.html   * 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
Line 92: Line 127:
== Desktop Team update - pitti ==
   
  * see: ?
  * Team status: https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
  * Work items: http://status.ubuntu.com/ubuntu-precise/canonical-desktop-team.html
== Unity Team update - popey ==
Line 98: Line 129:
== Desktop Experience Team Update - dbarth ==   * see:
  * plans: ??
Line 100: Line 132:
  * see: ?
  * Work items: (in progress, assessing bug workload)
== Kubuntu Team update - jr ==
Line 103: Line 134:
== Desktop Systems Engineering Update - Cami ==

  * 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 115: Line 139:
  * 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 118: Line 142:
== Xubuntu Team update - madnick == == Xubuntu Team update - knome or astraljava ==
Line 120: Line 144:
  * 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 125: Line 149:
  * 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 130: Line 154:
  * 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 135: Line 159:
  * see: ?   * Working on 12.04.1 LTS, not 12.10
Line 137: Line 161:
== MOTU Team Q&A - tumbleweed or Laney ==
Line 139: Line 162:
 * ? == MOTU Team Q&A - tumbleweed, iulian or Laney ==
Line 141: Line 164:
== 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 152: Line 172:
## * 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-05-15.00.moin.txt
 * Minutes (html):
http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-10-05-15.00.html
 * IRC log: http://irclogs.ubuntu.com/2012/10/05/%23ubuntu-meeting.html#t15:00

12.10 (Quantal Quetzal) Weekly Meeting

Upcoming Dates

Pending Actions

  • none

Release Overview

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

Community testing update - balloons

Security team update - mdeslaur

Kernel team update - ogasawara

Foundations team update - ogra

Server team update - arosales

Linaro update - fabo

Ubuntu One Team - joshuahoover

  • see:

Desktop Team update - seb128

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

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)