607
edits
Changes
Jump to navigation
Jump to search
Line 16:
Line 16: + + + + + + + + +
no edit summary
* Build a source tarball, test it carefully and make it available in a stable location.
* Build a source tarball, test it carefully and make it available in a stable location.
* Send an announce mail to announce@sugarlabs.org. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user targeted list of changes.
* Send an announce mail to announce@sugarlabs.org. The form will be decided by each maintainer but it should at least include a reference to the source code tarball and an high level, user targeted list of changes.
== Coordinated release ==
Each release cycle will include development, beta, release candidate and final releases. The release team is responsible to coordinate with module maintainers, pull the updated modules together, perform basic QA and announce it. More in detail:
* Ensure that all the module releases are available by the scheduled date.
* Construct a sugar-jhbuild moduleset out of them. Run automatic and manual QA on it.
* If issues arise coordinate with the relevant module maintainers to solve them.
* Announce the release on announce@sugarlabs.org, including a reference to the sugar-jhbuild moduleset, references to each source module and a global list of changes.
== Feature freeze ==
== Feature freeze ==