11.3.1/Release plan

From OLPC
Jump to navigation Jump to search

Scope and aims

  • Improve ARM support for XO-1.75
  • Complete runin coverage on XO-1.75
  • Solve some high impact known issues
  • Translations

Schedule

We aim to have "regression and platform fixes" cycle, following the second half of the Stabilization stage in our Release Process. The development phase is skipped completely, we start this cycle with frozen repositories.

The main drivers of the schedule are readiness of key ARM platform functionality (suspend/resume, audio), and manufacturing milestones (C2, ramp, MP).

C2 milestone stage -- platform fixes, regressions

  • Start date: November 1st 2011
  • End date: December 1st 2011
  • Duration: 4 weeks

Goals:

  • S/R stable enough for runin
  • Audio basically works in all activities
  • Basic power mgmt operations work - power btn to suspend/resume

Milestone builds will be signed.

Fedora updates will only be taken (selectively) when shown to fix regressions.

Sugar activity updates will only be taken (selectively) when shown to fix regressions.

We may also take trivial fixes to important problems (e.g. one-line fixes) where the risk is low.

Regression fixing stage

  • Start date: December 1st 2011
  • End date: December 20st 2011
  • Duration: 2 1/2 weeks

At this point, the project should have the "ready for release" feel. This final milestone is reserved for final testing. The only changes accepted here are fixes for regressions over previous OLPC OS releases.

Final release

  • Date: December 20th 2011

Work plan

Our work plan is centered around

  • OFW/EC -- focus on suspend/resume and core functionality
  • Kernel drivers -- suspend/resume, related power management, audio
  • XO-1.75 video driver
  • Sugar and Activities -- only high priority bugs

Risk areas

Schedule slippage, suspend/resume, audio.

Maintainability

Apart from exceptional circumstances, no new packages will be forked. This means all features have to go in through upstream channels. An upstream-first mentality will be maintained for the Sugar work:

  • Bug fix patches must already be in the relevant 0.92 branch of upstream git
  • Feature patches must already be in the relevant master branch of upstream git

Testing

Sam Greenfeld will maintain a spreadsheet recording when each of the basic functionalities have most recently been tested, and this will be shared with contributors. We will continue to engage the AU and NZ testing groups on the testing list. And we will try to clone their success with the formation of an OLPC testing group in Miami.

Trac conventions

All relevant bugs must be on http://dev.laptop.org for this release (as the focus is on non-sugar items).

Bugs on dev.laptop.org are marked as "add to build" when the solution has been packaged, and then set to "test in build" by the release manager once a build has been made. Sam Greenfeld (QA lead) is in charge of watching and closing those tickets.

Release management

Martin Langhoff will act as release manager, with help from Peter Robinson on builds and Simon Schampijer on triaging Sugar changes. Main workload willbe applying/enforcing the guidelines and milestones as above, approving the inevitable handful of exceptions, producing/announcing development builds, and coordinating release notes.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=11.3.1/Release_plan&oldid=262484"