Scheduled software release process: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 12: | Line 12: | ||
== OBJECTIVES == |
== OBJECTIVES == |
||
== DEVELOPMENT |
== DEVELOPMENT == |
||
== INTEGRATION == |
== INTEGRATION == |
Revision as of 23:50, 30 June 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.