2012-10-12

Differences between revisions 68 and 128 (spanning 60 versions)
Revision 68 as of 2012-05-24 21:48:25
Size: 6799
Editor: 99-191-111-134
Comment:
Revision 128 as of 2012-10-12 11:11:55
Size: 7451
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-10-05
Line 5: Line 6:
 * 2012/05/31 - FeatureDefinitionFreeze
 * 2012/06/07 - Alpha 1
 * 2012/06/21 - DebianImportFreeze
 * '''12.10'''
   * October 16 - [[https://wiki.ubuntu.com/FinalFreeze|Unseeded Universe Final Freeze]]
   * October 18 - '''12.10 Release'''

== Pending Actions ==

 * none
Line 11: Line 16:
 * Work Items for 12.10:
   * On blueprints, please remember to put all work items in the separate section.
   * All blueprints must be marked approved and targetted for the release to show up on the tracker.
 * 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
Line 15: Line 21:
   * There are XXXX on 2012/05/25, tracking line on status.ubuntu.com will be reset on FeatureDefinitionFreeze.
Line 18: Line 23:
   * current draft: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule
   * google calendar will be updated as soon as draft is removed from ReleaseSchedule:       http://fridge.ubuntu.com/calendars/ubuntu-release-calendar/
   * current: https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule
   * google calendar: http://fridge.ubuntu.com/calendars/ubuntu-release-calendar
Line 23: Line 27:
   * '''12.04.1''': http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html
     * Bugs labeled Critical are considered release blockers and need to be resolved ASAP.
   * Reminder: if you want a team to find and consider a bug quickly, '''please assign or subscribe the bug to that team''', if its not on the list for fixing, and you believe it should be, please work with the team's manager.
   * Bug tracking will be changing, see: https://blueprints.launchpad.net/ubuntu/+spec/other-q-release-bug-list-workflows
   * '''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'
Line 29: Line 38:

Based
on discussions at we'll be continuing with the open forum question and answer session for the weekly release meeting.

To make this efficient for everyone (and hopefully reduce confusion), would appreciate it if everyone tried to follow these conventions.
 
To make this meeting efficient for everyone (and hopefully reduce confusion), would appreciate it if everyone tried to follow these conventions.
Line 42: Line 49:
I'll try to call on folks in the order I see "o/"s showing up after the Q&A session starts. I'll try to call on folks in the order I see "o/"s showing up after the Q&C session starts.
Line 53: Line 60:
== QA team update - jibel == == QA team update - gema ==
Line 57: Line 64:
  * Upcoming tasks: https://launchpad.net/~canonical-platform-qa/+upcomingwork
Line 66: Line 74:
 * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-quality-community-testing.html
Line 69: Line 78:
  * see:     * see:
Line 71: Line 80:
  * Upcoming tasks: https://launchpad.net/~canonical-security/+upcomingwork
Line 75: Line 85:
  * Work items:      * http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-team.html
    *
http://status.ubuntu.com/ubuntu-quantal/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 80: Line 89:
== Foundations team update - cjwatson == == Foundations team update - ogra ==
Line 82: Line 91:
  * see:    * see:
Line 84: Line 93:
  * Armhf port: FTBFS - http://qa.ubuntuwire.org/ftbfs/primary-precise-armhf.html   * Upcoming tasks: https://launchpad.net/~canonical-foundations/+upcomingwork
Line 90: Line 99:
## * 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
    * 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
Line 101: Line 111:
  * Planning: https://launchpad.net/linaro-dev-platform/+milestone/12.06   * Planning: https://launchpad.net/linaro-dev-platform/+milestone/12.07
Line 107: Line 117:
Line 111: Line 120:
  * see:     * see:
Line 114: Line 123:
  * Upcoming tasks: https://launchpad.net/~canonical-desktop-team/+upcomingwork
Line 115: Line 125:
== Desktop Experience Team Update - dbarth == == Unity Team update - popey ==
Line 118: Line 128:
  * Work items: ??

== Desktop Systems Engineering Update - Cimi ==

  * see:
  * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-desktop-touch.html
  * plans: ??
Line 135: Line 140:
== Xubuntu Team update - madnick or knome == == Xubuntu Team update - knome or astraljava ==
Line 142: Line 147:
  * see:  
  * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntu-studio.html
  * see:
  * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntustudio.html
Line 152: Line 157:
  * see: ?   * Working on 12.04.1 LTS, not 12.10
Line 165: Line 170:
## * Minutes (wiki): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-03-16-16.00.moin.txt
## * Minutes (html): http://ubottu.com/meetingology/logs/ubuntu-meeting/2012/ubuntu-meeting.2012-03-16-16.00.html
## * IRC log:http://irclogs.ubuntu.com/2012/03/16/%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

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)