Child pages
  • Release Proposal 2009

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. an initial review of proposed new features (7)
    • determine which will need to go to the product council (and these will generally be for 2.8)
    • identify where more documentation is needed from development teams
    • make an initial risk assessment of various projects which can inform test planning (e.g. riskier changes may receive earlier QA focus)
    • establish realistic freeze dates for 2.7, based on time needed for QA, availability of resource, etc.
  2. the initial members of the release management team will work to propose (to the community) formal processes for how its decisions will be made and how members may be recruited
    Info
    titleFootnotes

    Anchor
    footnote1
    footnote1
    1. The new Product Development Process introduces new roles and new ways of doing business. There is a newly appointed product council, which will be working to establish a transparent process with clear criteria, and there is also a new product manager, among whose responsibilities is ownership of a Sakai roadmap. The new process is not going to achieve maturity overnight, especially at this time of year when both vacations and Fall term preoccupations hold sway, and so a balance needs to be struck that allows the council begin taking up its charge quickly but simply, without throwing all expectations and ingrained habits into sudden confusion.

    Anchor
    footnote2
    footnote2
    2. The community needs a reliable release roadmap in order to both contribute to the general effort and make preparations for its own deployments.

    Anchor
    footnote3
    footnote3
    3. Release scope will be framed by an analysis of what can be managed and adequately tested under the constraints of available time and volunteer resource from the community. Functional priorities will require the guidance of the product council, but against this an achievable release management plan still needs to be developed, and on this basis some proposed new features may have to be postponed for a future release.

    Anchor
    footnote4
    footnote4
    4. These two releases would correspond roughly to two different kinds of processes for reviewing release readiness of new development work. A "lightweight" process can be used for modest refinements or small additions to existing functionality, and typically won't involve the product council. A "heavy" process would involve passage through the entire product development cycle. Changes to existing functionality that the release management team deems significant (e.g. a big change to the UX, or involving some considerable technical risk) will be brought before the review of the product council by the product manager.

    Anchor
    footnote5
    footnote5
    5. While QA and other release management processes are underway for 2.7, review and planning for 2.8 will also begin. To the extent that 2.8 involves significant new capabilities, this activity will happen mostly in the context of product council processes.

    Anchor
    footnote6
    footnote6
    6. The meetings will publish minutes, document decisions, and send out any significant proposals to the list for community comment.

    Anchor
    footnote7
    footnote7
    7. New features and plans from development teams are being collected in Confluence at: Proposed changes to 2.7