2012-10-12

Differences between revisions 67 and 68
Revision 67 as of 2012-05-24 20:26:46
Size: 6602
Editor: 99-191-111-134
Comment:
Revision 68 as of 2012-05-24 21:48:25
Size: 6799
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-04-13
## page was copied from ReleaseTeam/Meeting/2012-04-06
= 12.04 LTS (Precise Pangolin) Weekly Meeting =
= 12.10 (Quantal Quetzal) Weekly Meeting =
Line 7: Line 5:
 * 2012/04/05 - Kernel freeze, and archive refreezes.
 * 2012/04/12 -
final freeze
 * 2012/04/19 - release candidate
 * 2012/04/26 - release!
 * 2012/05/31 - FeatureDefinitionFreeze
 * 2012/06/07 - Alpha 1
 * 2012/06/21 - DebianImportFreeze
Line 14: Line 11:
 * Work Items for 12.04:
   * There are now XXXX on 2012/03/21 (2084 on 2011/11/25).
   * please review your blueprints for those work items.
     * if it takes 10 minutes to do a task - please do it and update.
     * its clear won't happen this release, and set them to POSTPONED.
 * 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.
   * Suggested format to use for blueprints that are for feature development is: BlueprintSpec
   * There are XXXX on 2012/05/25, tracking line on status.ubuntu.com will be reset on FeatureDefinitionFreeze.
Line 20: Line 17:
 * Precise Schedule:
   * see: https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
   * google calendar: http://fridge.ubuntu.com/calendars/ubuntu-release-calendar/
 * Quantal Schedule:
   * 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/
Line 25: Line 23:
   * '''Current list''': http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html    * '''12.04.1''': http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/rls-p-tracking-bugs.html
Line 28: Line 26:
   * Bug tracking will be changing, see: https://blueprints.launchpad.net/ubuntu/+spec/other-q-release-bug-list-workflows
Line 29: Line 28:
== New Meeting Format - Experiment == == Meeting Format ==
Line 31: Line 30:
For the remainder of the release we'll be using the new forma of an open forum question and answer session for the weekly release meeting. Based on discussions at we'll be continuing with the open forum question and answer session for the weekly release meeting.
Line 50: Line 49:
== Hardware Certification team update - ara == == Hardware Certification team update - brendand ==
Line 57: Line 56:
  * Work items: http://status.ubuntu.com/ubuntu-precise/canonical-platform-qa.html   * Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-platform-qa.html
Line 60: Line 59:
    * 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 63: Line 62:

== Community testing update - balloons ==

 * see:
Line 67: Line 70:
  * 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
Line 73: Line 76:
    * 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
    * http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-team.html
    * http://status.ubuntu.com/ubuntu-quantal/canonical-kernel-distro-team.html
Line 81: Line 83:
  * Work items:http://status.ubuntu.com/ubuntu-precise/canonical-foundations.html   * Work items:http://status.ubuntu.com/ubuntu-quantal/canonical-foundations.html
Line 88: Line 90:
    * 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
    * 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:
## * 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
Line 94: Line 96:

Line 101: Line 101:
  * Planning: https://launchpad.net/linaro-dev-platform/+milestone/11.12   * Planning: https://launchpad.net/linaro-dev-platform/+milestone/12.06
Line 106: Line 107:
Line 107: Line 109:
== Desktop Team update - pitti == == Desktop Team update - seb128 ==
Line 111: Line 113:
  * Work items: http://status.ubuntu.com/ubuntu-precise/canonical-desktop-team.html   * Work items: http://status.ubuntu.com/ubuntu-quantal/canonical-desktop-team.html
Line 121: Line 123:
  * Work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-desktop-touch.html   * Work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-desktop-touch.html
Line 123: Line 125:
== Kubuntu Team update - Riddell == == Kubuntu Team update - jr ==
Line 126: Line 128:
  * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-kubuntu.html   * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-kubuntu.html
Line 131: Line 133:
  * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-edubuntu.html   * work items: http://status.ubuntu.com/ubuntu-quanatal/group/topic-quantal-flavor-edubuntu.html
Line 136: Line 138:
  * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-xubuntu.html   * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-xubuntu.html
Line 141: Line 143:
  * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-ubuntu-studio.html   * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-ubuntu-studio.html
Line 146: Line 148:
  * work items: http://status.ubuntu.com/ubuntu-precise/group/topic-precise-flavor-lubuntu.html   * work items: http://status.ubuntu.com/ubuntu-quantal/group/topic-quantal-flavor-lubuntu.html
Line 152: Line 154:
== MOTU Team Q&A - tumbleweed or Laney ==
== MOTU Team Q&A - tumbleweed, iulian or Laney ==

12.10 (Quantal Quetzal) Weekly Meeting

Upcoming Dates

Release Overview

Meeting Format

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.

  • 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

Community testing update - balloons

  • see:

Security team update - mdeslaur

Kernel team update - ogasawara

Foundations team update - cjwatson

Server team update - arosales

  • see:
  • Work items:

Linaro update - fabo

Ubuntu One Team - joshuahoover

  • see:

Desktop Team update - seb128

Desktop Experience Team Update - dbarth

  • see:
  • Work items: ??

Desktop Systems Engineering Update - Cimi

Kubuntu Team update - jr

Edubuntu Team update - stgraber or highvoltage

Xubuntu Team update - madnick or knome

Ubuntu Studio update - scott-work

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-12 (last edited 2012-10-12 11:11:55 by 99-191-111-134)