Scheduled software release process: Difference between revisions
Jump to navigation
Jump to search
(Placeholder text.) |
(First layer.) |
||
| Line 1: | Line 1: | ||
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. |
|||
This procedure has not yet been written. |
|||
= Process Overview = |
|||
For suggestions, see the [http://live.gnome.org/ReleasePlanning GNOME release process]. |
|||
# [[#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. |
|||
# [[#INTEGRATION|INTEGRATION]]: Generate and execute a release contract for each desired change. |
|||
# [[#RELEASE|RELEASE]]: Execute the [[Software ECO process]] to deliver the release. |
|||
Revision as of 23:48, 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.