Changes

* Short description of the features.

* Short description of the features.

* Screenshots or screencasts.

* Screenshots or screencasts.

* Are you willing to follow the [[ReleaseTeam/Roadmap#Schedule|Schedule]]?

* Are you willing to follow the [[DevelopmentTeam/Release/Roadmap#Schedule|Schedule]]?

* Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations)

* Are you willing to provide regular source releases? (releases need to be done as well when there are only changes in translations)

* System components the activity depends on.

* System components the activity depends on.

== Feature freeze ==

== Feature freeze ==

The feature freeze affects all the modules included in the release and comprise also strings and ABI for public libraries. Exceptions might be considered by the release team but they will be extremely rare. To request an exception send mail to [http://lists.laptop.org/mailman/listinfo/sugar sugar@laptop.org], referencing the patches you would like to land. It will have to be granted by two [[ReleaseTeam/Contacts|members]] of the release team, on the base of community feedback. For string changes please also copy [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org]. As soon as the change is committed in git, notify the localization list about it.

The feature freeze affects all the modules included in the release and comprise also strings and ABI for public libraries. Exceptions might be considered by the release team but they will be extremely rare. To request an exception send mail to [http://lists.laptop.org/mailman/listinfo/sugar sugar@laptop.org], referencing the patches you would like to land. It will have to be granted by two [[DevelopmentTeam/Release/Contacts|members]] of the release team, on the base of community feedback. For string changes please also copy [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org]. As soon as the change is committed in git, notify the localization list about it.

== Hard code freeze ==

== Hard code freeze ==

When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar@laptop.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two [[ReleaseTeam/Contacts#People|members]] of the team.

When the hard code freeze is in effect, each and every code change should be approved by the release team. Only critical fixes will be considered. To request approval send mail to sugar@laptop.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two [[DevelopmentTeam/Release/Contacts#People|members]] of the team.

== Branching ==

== Branching ==

== Roadmap ==

== Roadmap ==

The [[ReleaseTeam/Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:

The [[DevelopmentTeam/Release/Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:

* Detailed schedule of release dates and freeze points.

* Detailed schedule of release dates and freeze points.

TBD Many of the steps described in this document can be easily automated for maintainers which are using the Sugar Labs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.

TBD Many of the steps described in this document can be easily automated for maintainers which are using the Sugar Labs infrastructure and for the release team. Though as a first pass we want to get the workflow right, even if it involves more manual step than strictly required.

[[Category:ReleaseTeam]]

[[Category:DevelopmentTeam/Release]]