Changes

=== New modules proposal ===

=== New modules proposal ===

The time period available to make a proposal is indicated on the schedule. To propose a new activity send mail to the [http://lists.laptop.org/listinfo/sugar sugar mailing list], providing the following informations:

The time period available to make a proposal is indicated on the schedule. To propose a new activity send mail to the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org], providing the following informations:

* Short description of the features.

* Short description of the features.

* Build a source tarball, test it carefully and make it available in a stable location. The preferred location is http://dev.laptop.org/pub/sugar/sources/ which translates to: dev.laptop.org:/var/www/sugar/sources/ You need a developer account to be able to upload there.

* Build a source tarball, test it carefully and make it available in a stable location. The preferred location is http://dev.laptop.org/pub/sugar/sources/ which translates to: dev.laptop.org:/var/www/sugar/sources/ You need a developer account to be able to upload there.

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20 for an activity, v0.81.9 for a Glucose module).

* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20 for an activity, v0.81.9 for a Glucose module).

* Send an announce mail to sugar@laptop.org, with [RELEASE] in the subject. 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 oriented list of changes.

* Send an announce mail to sugar-devel@lists.sugarlabs.org, with [RELEASE] in the subject. 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 oriented list of changes.

=== Activity sources ===

=== Activity sources ===

* Construct a sugar-jhbuild moduleset out of them. Run automatic and manual QA on it.

* 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.

* If issues arise coordinate with the relevant module maintainers to solve them.

* Announce the release on sugar@laptop.org, including a reference to the sugar-jhbuild moduleset, references to each source module and a global list of changes.

* Announce the release on sugar-devel@lists.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 ==

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.

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.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.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 [[DevelopmentTeam/Release/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-devel@lists.sugarlabs.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 ==

After the final release of a module, a branch should be created to host further stable development. Please use name in the sucrose-XXX form (for example sucrose-0.82). Each module maintainer is responsible to inform the [http://lists.laptop.org/mailman/listinfo/sugar sugar@laptop.org] and [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org] lists about the branch.

After the final release of a module, a branch should be created to host further stable development. Please use name in the sucrose-XXX form (for example sucrose-0.82). Each module maintainer is responsible to inform the [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] and [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org] lists about the branch.

You can create a remote branch like this:

You can create a remote branch like this: