User:Mstone/Commentaries/Releases 3: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (New page: We make changes to our software for many reasons; however, we make scheduled (major) releases in order to deliver significant changes to our downstream clients. Major releases may include ...)
 
mNo edit summary
Line 1: Line 1:
{{Draft}}

We make changes to our software for many reasons; however, we make scheduled (major) releases in order to deliver significant changes to our downstream clients. Major releases may include interface-breaking changes. They are different from [[Unscheduled software release process|unscheduled (minor) releases]] in that they contain larger and more thoroughly planned changes.
We make changes to our software for many reasons; however, we make scheduled (major) releases in order to deliver significant changes to our downstream clients. Major releases may include interface-breaking changes. They are different from [[Unscheduled software release process|unscheduled (minor) releases]] in that they contain larger and more thoroughly planned changes.


Line 5: Line 7:
# [[#OBJECTIVES|OBJECTIVES]]: Choose a target month. Solicit goals and priorities for the release. Propose ends and means.
# [[#OBJECTIVES|OBJECTIVES]]: Choose a target month. Solicit goals and priorities for the release. Propose ends and means.
# [[#DEVELOPMENT|DEVELOPMENT]]: Generate changes which may help to meet the new goals.
# [[#DEVELOPMENT|DEVELOPMENT]]: Generate changes which may help to meet the new goals.
# [[#INTEGRATION|INTEGRATION]]: Generate and execute a release contract for each desired change.
# [[#RELEASE|RELEASE]]: Generate and execute a release contract for each desired change. Execute the [[Software ECO process]] to deliver the release.
# [[#RELEASE|RELEASE]]: Execute the [[Software ECO process]] to deliver the release.
# [[#DEPLOYMENT|DEPLOYMENT]]: Help downstream partners adapt to the new release.



= Process Step Details =
= Process Step Details =
Line 25: Line 28:
We have learned that certain minimum amounts of time must be allocated to integration and testing. The following example schedule records some of this knowledge:
We have learned that certain minimum amounts of time must be allocated to integration and testing. The following example schedule records some of this knowledge:


# >90 days before target date '''Steam'''. Changes can be proposed at will and ''should'' be proposed as early as possible.
# >90-60 days before target date '''Steam'''. Changes can be proposed at will and ''should'' be proposed as early as possible.
# 60 days before target date '''Water'''. Proposals must pass muster with the release team. Release contracts should be written and integration should occur. This is ''feature-level change control''.
# 60-30 days before target date '''Water'''. Proposals must pass muster with the release team. Release contracts should be written and integration should occur. This is ''feature-level change control''.
# 30 days before target date '''Ice'''. We branch for release and the release team produces release candidates as needed under ''package-level change-control''. Developers should be focused on fixing bugs.
# 30 days before target date '''Ice'''. We branch for release and the release team produces release candidates as needed under ''package-level change-control''. Developers should be focused on fixing bugs.
# <15 days before target date '''Final Test'''. Get consensus from test, QA, and engineering communities, then finish the [[USR_Checklist|Release Process Checklist]].
# <15 days before target date '''Final Test'''. Get consensus from test, QA, and engineering communities, then finish the [[USR_Checklist|Release Process Checklist]].
# Release day. '''Announcement Day'''. Once Release checklist is complete, Kim sends announcement e-mail approving release for production.
# Release day. '''Announcement Day'''. Once Release checklist is complete, Kim sends announcement e-mail approving release for production.





== DEVELOPMENT ==
== DEVELOPMENT ==


Development consists of creating potentially releasable changes during a period of '''No Change Control''' and a period of '''Light Change Control'''.
Development consists of creating potentially releasable changes during a ''Steam'' period (no change control) and a ''Water'' period (feature-level change control).


=== STEAM ===
=== STEAM ===
''MORE than 60 days before target date''
'''Occurs:''' ''MORE than 60 days before target date''

⚫
Prior to the transition to ''Water'' (feature-level change control), there is great freedom to propose changes because resources have not been allocated toward integrating and testing the proposed changes. We allocate these resources with [[Scheduled software release process#Contracts|release contracts]].


⚫
Prior to ''Water'' (feature-level change control), there is great freedom to propose changes because resources have not been allocated toward integrating and testing the proposed changes. We allocate these resources with [[Scheduled software release process#Contracts|release contracts]].


=== WATER ===
=== WATER ===
''60-30 days before target date''
'''Occurs:''' ''60-30 days before target date''


When ''Steam'' transitions to ''Water'', changes requiring reallocation of integration, test, or downstream resources (i.e. requiring a new release contract) will require approval by module maintainers and Release Management before being accepted. Minor changes can still be added without approval for another 15 days. Changes requiring great coordination to deliver like string changes and UI changes will be deferred if possible.
When ''Steam'' transitions to ''Water'', changes requiring reallocation of integration, test, or downstream resources (i.e. requiring a new release contract) will require approval by module maintainers and Release Management before being accepted. Minor changes can still be added without approval until the transition to ''Ice''. Changes requiring great coordination to deliver like string changes and UI changes will be deferred if possible.


By the end of ''Water'', developers are expected to have:
== INTEGRATION ==


* Create release contracts for each desired change. See [http://dev.laptop.org/report/18 previous examples].
* Created release contracts for each desired change. See [http://dev.laptop.org/report/18 previous examples].
* Combine potentially releasable changes and fix any resulting bugs.


== RELEASE ==
=== Medium Change Control ===


Release consists of integrating desirable changes created during development, then executing the [[Software ECO process]] to finalize the result.


All translation packages must be final by this time. <br>
On or before this date Module maintainers propose a set of bug fixes to get into the testing branch. They usually do so by releasing a new version of their module and informing the release team about the changes it contains and the steps necessary to test those. The release team will make sure that
the relevant QA is executed and either approve the changes or ask for fixes/improvements. As soon as the changes are approved they are added to the testing build. After this date no changes are allowed in to the code without the approval of the module maintainer and the [[Unscheduled_software_release_process#Triage_Team|Release Triage team]].


== RELEASE ==
=== ICE ===
'''Occurs:''' ''30-0 days before target date''

When ''Water'' transitions to ''Ice'', the release team will branch the development stream twice creating ''updates'' and ''testing'' build streams.

* Both the ''updates'' and ''testing'' streams will be placed under package-level change control by the release team.
* The ''updates'' stream will be used to house packages being considered by the release team for insertion into the ''testing'' stream.
* Official QA will consider builds from the ''testing'' stream. When approved by official QA, these builds can become [[Software ECO process#CANDIDATE BUILD|release candidates]] as part of the underlying [[Software ECO process]] being executed by the release team.

== DEPLOYMENT ==


Upon completion of the [[Software ECO process]], a new reference operating system is made available. However, further work must be done to adapt this component to the needs of downstream partners.
Execute the [[Software ECO process]] to deliver the release.

Revision as of 03:40, 1 July 2008


Pencil.png NOTE: The contents of this page are not set in stone, and are subject to change!

This page is a draft in active flux ...
Please leave suggestions on the talk page.

Pencil.png

We make changes to our software for many reasons; however, we make scheduled (major) releases in order to deliver significant changes to our downstream clients. Major releases may include interface-breaking changes. They are different from unscheduled (minor) releases in that they contain larger and more thoroughly planned changes.

Process Overview

  1. OBJECTIVES: Choose a target month. Solicit goals and priorities for the release. Propose ends and means.
  2. DEVELOPMENT: Generate changes which may help to meet the new goals.
  3. RELEASE: Generate and execute a release contract for each desired change. Execute the Software ECO process to deliver the release.
  4. DEPLOYMENT: Help downstream partners adapt to the new release.


Process Step Details

OBJECTIVES

Write an Objectives page (e.g. 8.2.0) recording a consensus on:

  • target month.
  • development goals and priorities.
  • lead customers.
  • feasibility of proposed changes.

Module maintainers, product management, and the release team will be responsible for building and maintaining this consensus based on communal, customer, and institutional feedback. All three groups will be responsible for acting to achieve its mandates, e.g. as advisers, maintainers, and managers.

Schedule

We have learned that certain minimum amounts of time must be allocated to integration and testing. The following example schedule records some of this knowledge:

  1. >90-60 days before target date Steam. Changes can be proposed at will and should be proposed as early as possible.
  2. 60-30 days before target date Water. Proposals must pass muster with the release team. Release contracts should be written and integration should occur. This is feature-level change control.
  3. 30 days before target date Ice. We branch for release and the release team produces release candidates as needed under package-level change-control. Developers should be focused on fixing bugs.
  4. <15 days before target date Final Test. Get consensus from test, QA, and engineering communities, then finish the Release Process Checklist.
  5. Release day. Announcement Day. Once Release checklist is complete, Kim sends announcement e-mail approving release for production.


DEVELOPMENT

Development consists of creating potentially releasable changes during a Steam period (no change control) and a Water period (feature-level change control).

STEAM

Occurs: MORE than 60 days before target date

Prior to the transition to Water (feature-level change control), there is great freedom to propose changes because resources have not been allocated toward integrating and testing the proposed changes. We allocate these resources with release contracts.


WATER

Occurs: 60-30 days before target date

When Steam transitions to Water, changes requiring reallocation of integration, test, or downstream resources (i.e. requiring a new release contract) will require approval by module maintainers and Release Management before being accepted. Minor changes can still be added without approval until the transition to Ice. Changes requiring great coordination to deliver like string changes and UI changes will be deferred if possible.

By the end of Water, developers are expected to have:

RELEASE

Release consists of integrating desirable changes created during development, then executing the Software ECO process to finalize the result.


ICE

Occurs: 30-0 days before target date

When Water transitions to Ice, the release team will branch the development stream twice creating updates and testing build streams.

  • Both the updates and testing streams will be placed under package-level change control by the release team.
  • The updates stream will be used to house packages being considered by the release team for insertion into the testing stream.
  • Official QA will consider builds from the testing stream. When approved by official QA, these builds can become release candidates as part of the underlying Software ECO process being executed by the release team.

DEPLOYMENT

Upon completion of the Software ECO process, a new reference operating system is made available. However, further work must be done to adapt this component to the needs of downstream partners.

Retrieved from "http://wiki.laptop.org/mediawiki/index.php?title=User:Mstone/Commentaries/Releases_3&oldid=142342"