8.2.0: Difference between revisions

From OLPC
Jump to navigation Jump to search
Line 29: Line 29:
: '''8/27''': we will nominate a build as our '''Alpha image''' for maximal testing. If miracles occur, it will have no blockers. :)
: '''8/27''': we will nominate a build as our '''Alpha image''' for maximal testing. If miracles occur, it will have no blockers. :)


: '''9/03''': change control tightens (i.e. '''"we freeze"''').
: '''9/03''': [[#Change Control|change control]] tightens (i.e. '''"we freeze"''').


: '''9/05''': we will officially '''refresh translations'''.
: '''9/05''': we will officially '''refresh translations'''.

Revision as of 01:58, 23 August 2008

8.2.0 is a future release in development and early testing (as of July 2008). Here are its (draft) release notes.

Terminology

blocker
We can agree on a minimal set of bugs which are so nasty that we know in advance that we could never deploy an OS containing them. These bugs are called 'blockers'. We will not ship 8.2.0 with open blockers.
See 8.2.0 blockers and proposed 8.2.0 blockers.
polish
We can agree on a more inclusive set of low-risk 'polish' bugs that we should attempt to resolve as time and resources permit.
See 8.2.0 polish opportunities.
milestones
Our ideal 8.2.0 release procedure will consist of motion toward the delivery of three milestone builds:
  • an Alpha image with few blockers,
  • a signed Beta image with some polish, and
  • a signed Final image with no blockers and, we hope, some polish.
change control
A process for limiting the rate of change and restricting the causes of change to a deliverable (like an OS build) so that correlated deliverables (like release notes) can be synchronized.
a.k.a "freezing"

Schedule

Preparations for the 8.2.0 release began in December, 2007 and rapidly expanded in March, 2008 when, having completed the 8.1.0 release, the Sugar team began working toward the goal of shipping their UI redesign. In March, it was decided to try to ship the release in August according to documented development priorities on the basis of the claim that August was the earliest time at which the integration of a useful body of features could be completed. The current schedule calls for the completion of the 8.2.0 release in mid-September as follows:

m/dd
8/27: we will nominate a build as our Alpha image for maximal testing. If miracles occur, it will have no blockers. :)
9/03: change control tightens (i.e. "we freeze").
9/05: we will officially refresh translations.
9/07: we will conduct a preliminary security audit of the OFW, EC, kernel, and initramfs changes relevant to initial activation security.
9/10: we will publish a signed Beta reference OS and G1G1 derivative images.
9/17: we will publish the signed Final images of the 8.2.0 reference OS, release notes, and the G1G1 derivative image.

End-game Priorities

  1. PLEASE RESOLVE BLOCKERS:
  2. OTHERWISE, help out with the TESTING effort:
  3. OTHERWISE, help out with the DAILY TRIAGE and RELEASE-NOTING effort:
  4. OTHERWISE, UNTIL 9/03, you can POLISH:

Change Control

Change control will be in force on the 8.2.0 release stream from now until release and will be managed by Scott, Marco, and Michael.
From 8/20 to 9/03, light change control ('slush', 'frost') will be in place. During this interval, changes to the release stream must be approved, in any medium, by Scott, Marco, or Michael before being pushed. Changes will not be approved without detailed ChangeLog entries (e.g. as good as Scott's commit messages).
From 9/03 to 9/17, full change control ('ice', 'frozen') will be in place. No changes will be accepted unless they are explicitly coordinated and scheduled by the full release team.

Development stream

We have a pilgrim stream named "8.2" which is where release candidates will be developed.

Builds are manually triggered by C. Scott Ananian.

Release Criteria

The release criteria for 8.2.0 are being drafted and will be posted shortly.

Useful Links

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=8.2.0&oldid=154047"