Scheduled software release process: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 11: | Line 11: | ||
== OBJECTIVES == |
== OBJECTIVES == |
||
Write an Objectives page, similar to [[8.2.0]], recording: |
|||
* the target month. |
|||
* development goals and priorities. |
|||
* lead customers. |
|||
* feasibility of proposed changes. |
|||
== DEVELOPMENT == |
== DEVELOPMENT == |
||
Create potentially releasable changes. |
|||
== INTEGRATION == |
== INTEGRATION == |
||
* Create 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 == |
== RELEASE == |
||
Execute the [[Software ECO process]] to deliver the release. |
|||
Revision as of 00:03, 1 July 2008
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
- OBJECTIVES: Choose a target month. Solicit goals and priorities for the release. Propose ends and means.
- DEVELOPMENT: Generate changes which may help to meet the new goals.
- INTEGRATION: Generate and execute a release contract for each desired change.
- RELEASE: Execute the Software ECO process to deliver the release.
Process Step Details
OBJECTIVES
Write an Objectives page, similar to 8.2.0, recording:
- the target month.
- development goals and priorities.
- lead customers.
- feasibility of proposed changes.
DEVELOPMENT
Create potentially releasable changes.
INTEGRATION
- Create release contracts for each desired change. See previous examples.
- Combine potentially releasable changes and fix any resulting bugs.
RELEASE
Execute the Software ECO process to deliver the release.