8.2.0: Difference between revisions
| Line 39: | Line 39: | ||
: '''Approx 9/17''': we will publish '''Beta image, RC2''' reference OS and G1G1 derivative images. Ideally this is the final candidate and it needs 2 weeks of testing and documentation. |
: '''Approx 9/17''': we will publish '''Beta image, RC2''' reference OS and G1G1 derivative images. Ideally this is the final candidate and it needs 2 weeks of testing and documentation. |
||
: '''Approx 9/24''': we will publish '''RC3''', only if needed; finish |
: '''Approx 9/24''': we will publish '''RC3''', only if needed; finish the [[Release Notes/8.2.0|release notes]], and the G1G1 derivative images. |
||
: '''Final Release''': by end of September. |
: '''Final Release''': by end of September. |
||
Revision as of 15:24, 2 September 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:
These dates are subject to change and not confirmed or finalized.
- m/dd
- 8/27: we will nominate a build as our Alpha image, RC1 for maximal testing.
- 9/03: change control tightens (i.e. "we freeze").
- 9/05: we will officially refresh translations and new Sugar.
- 9/07: we will start the security audit of the OFW, EC, kernel, and initramfs changes relevant to initial activation security.
- Approx 9/17: we will publish Beta image, RC2 reference OS and G1G1 derivative images. Ideally this is the final candidate and it needs 2 weeks of testing and documentation.
- Approx 9/24: we will publish RC3, only if needed; finish the release notes, and the G1G1 derivative images.
- Final Release: by end of September.
These dates are subject to change and not confirmed or finalized.
End-game Priorities
- PLEASE RESOLVE BLOCKERS:
- Report of 8.2.0 blockers.
- Even if they aren't assigned to you, please help!!!
- OTHERWISE, help out with the TESTING effort:
- Systematic testing (not yet ready)
- Friends in testing
- OTHERWISE, help out with the DAILY TRIAGE and RELEASE-NOTING effort:
- http://tinyurl.com/5zj4cs
- Report of bugs proposed as 8.2.0 blockers
- 1500 UTC on #olpc-meeting
- 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 final release, 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.
- See User:Gregorio/8.2.0 release criteria for Greg's wishlist.
Useful Links
- Trac queries#8.2.0 Queries -- currently interesting bugtracker queries.
- Trac conventions -- tagging conventions used in trac to indicate important aspects of bugs.
- Trac ticket workflow -- typical workflow states through which tickets pass.
- Release notes/8.2.0 -- release notes.
- OLPC 8.2.0 Features -- features list.
- Test cases 8.2.0 -- 8.2.0 test cases.