243
edits
Changes
Jump to navigation
Jump to search
Line 87:
Line 87: − + + + + + + + + + + Line 94:
Line 103: − + Line 101:
Line 110: − + − + − + − + − + Line 131:
Line 140: − == Roadmap == − − The Development Team's [[{{Upcoming Stable Release}}/Roadmap|Roadmap]] is updated at the beginning of each release cycle by the release team. It includes: − − * Detailed schedule of release dates and freeze points. − * List of modules and external dependencies. − * Reference to all the tickets considered for the release. − * References to the new feature proposals.
make components of release cycle subheadings of the release cycle heading
* 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.
* 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 ==
=== Roadmap Update ===
The Development Team's [[{{Upcoming Stable Release}}/Roadmap|Roadmap]] is updated at the beginning of each release cycle by the release team. It includes:
* Detailed schedule of release dates and freeze points.
* List of modules and external dependencies.
* Reference to all the tickets considered for the release.
* References to the new feature proposals.
=== Feature freeze ===
No new modules or features will be accepted for this release period. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.
No new modules or features will be accepted for this release period. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.
The feature freeze affects all the modules included in the release and comprise also 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 [[Development Team/Release/Contacts|members]] of the release team, on the base of community feedback.
The feature freeze affects all the modules included in the release and comprise also 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 [[Development Team/Release/Contacts|members]] of the release team, on the base of community feedback.
== UI Freeze ==
=== UI Freeze ===
Major UI revisions or changes must be done before this date. You can still make string changes (e.g. changing a sentence in a window) before the String Freeze.
Major UI revisions or changes must be done before this date. You can still make string changes (e.g. changing a sentence in a window) before the String Freeze.
If you really need to do an UI change you have to ask an exception from the release team and must notify the documentation team when accepted.
If you really need to do an UI change you have to ask an exception from the release team and must notify the documentation team when accepted.
== String cooling==
=== String cooling===
String changes have to be announced, but no exceptions have to be requested. As soon as the change is committed in git, notify the [[http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] about it.
String changes have to be announced, but no exceptions have to be requested. As soon as the change is committed in git, notify the [[http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] about it.
== String Freeze==
=== String Freeze===
Every string change has to be requested and to be approved. Please send an exception to the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] and [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] if you need to break the string freeze and ask for an exception. The localization team lead and two members of the release team need to approve such a break.
Every string change has to be requested and to be approved. Please send an exception to the [http://lists.laptop.org/mailman/listinfo/localization localization@lists.laptop.org localization list] and [http://lists.sugarlabs.org/listinfo/sugar-devel sugar-devel@lists.sugarlabs.org] if you need to break the string freeze and ask for an exception. The localization team lead and two members of the release team need to approve such a break.
== Stabilizing ==
=== Stabilizing ===
In the stabilizing phase we request every bug fix to be tied to a ticket including a testing plan. Please add the testcase in the ticket comment field. You need to mark it with |TestCase|. This adds better readability and our script that pulls together the test cases for each release is able to find it as well. For example:
In the stabilizing phase we request every bug fix to be tied to a ticket including a testing plan. Please add the testcase in the ticket comment field. You need to mark it with |TestCase|. This adds better readability and our script that pulls together the test cases for each release is able to find it as well. For example:
|TestCase|
|TestCase|
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.
Click on Browse, Read, Pippy icons in the homepage and make sure all of them starts correctly.
== 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-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 [[Development Team/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 [[Development Team/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 a name in the form: sucrose-XXX (for example sucrose-0.84). 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.
After the final release of a module, a branch should be created to host further stable development. Please use a name in the form: sucrose-XXX (for example sucrose-0.84). 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.
git pull
git pull
== Bug triaging ==
== Bug triaging ==