1,285
edits
Changes
Jump to navigation
Jump to search
Line 39:
Line 39: − + − + − make distcheck+ − + − + − + − + − + − + − + − + − + − + − − + − If your activity uses bundlebuilder you can use the dist_source command to generate a source tarball. Note, use a clean checkout of the repository - due to how bundlebuilder works at the moment files you would place in the directory e.g. x.patch would be included in the tarball as well.+ − − + − The tarball will be generated inside the dist directory.+ − + − + − + − + − − + − + − + − + + − + Line 115:
Line 113: − + − + − + Line 129:
Line 127: − By Feature Freeze all new features have to be complete, reviewed and pushed to the repository. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.+ Line 136:
Line 134: − Major UI revisions or changes must be done before this date.+ Line 143:
Line 141: − 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.+ − After this date 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.+ − 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:+ − + − +
Development Team/Release (view source)
Revision as of 17:14, 14 September 2017
, 17:14, 14 September 2017→Glucose (base) modules
{{Anchor|Glucose}}
{{Anchor|Glucose}}
=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> (base) modules===
=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> (base) modules===
* Build a source tarball
* Check out the repository branch,
* Create a git tag to reference the release. The tag should be in the vXXX form (for example v0.111).
git tag v0.111
* Build a source tarball from the branch,
* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v0.81.9).
make distcheck
* Test the source tarball carefully, using {{Code|configure}}, {{Code|make}}, {{Code|make install}}, and any packaging technology you are familiar with,
* test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there. The preferred location for glucose modules is:
* Upload the source tarball to a stable location. You need a developer account with Sugar Labs to be able to upload there. The location for glucose modules is:
shell.sugarlabs.org:/upload/sources/sucrose/glucose/(module_name)/
shell.sugarlabs.org:/upload/sources/sucrose/glucose/ (module_name)/
which translates to:
which translates to:
http://download.sugarlabs.org/sources/sucrose/glucose/(module_name)/
http://download.sugarlabs.org/sources/sucrose/glucose/ (module_name)/
* Push the release tag to the project repository,
* 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.
git push --tags
* Announce by 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 a high level, user oriented list of changes.
* Update the Activity Library default stable release; the variable SITE_SUGAR_STABLE in site/app/config/config.php then check on activities.sugarlabs.org with a browser other than Browse that an activity compatible with the release is listed.
* When the {{Code|sugar}} module is released, update the Activity Library default stable release; the variable {{Code|SITE_SUGAR_STABLE}} in site/app/config/config.php then check on [https://activities.sugarlabs.org activities.sugarlabs.org] with a browser other than Browse that an activity compatible with the release is listed.
{{Anchor|Fructose}}
{{Anchor|Fructose}}
===<abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> (base activity) modules===
===<abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> (base activity) modules===
* Build a source tarball
* Check out the branch of the project repository,
* Make the source tarball and bundle, which for most activities is done by {{Code|bundlebuilder}} via {{Code|setup.py}} and will place the result in the {{Code|dist/}} directory:
python setup.py dist_source
python setup.py dist_source
python setup.py dist_xo
ls -l dist/
* Create a git tag to reference the release. The tag name should be in the vXXX form (for example v20).
* In git add a tag to reference the release. The tag name should be in the vXXX form (for example v20).
git tag v20
* Test it carefully, to make sure it starts inside Sugar,
* Test it carefully and make it available in a stable location. You need a developer account with Sugar Labs to be able to upload there.
* Upload the tarball to a stable location. You need a developer account with Sugar Labs to be able to upload there.
The preferred location for fructose components is:
The preferred location for fructose components is:
shell.sugarlabs.org:/upload/sources/sucrose/fructose/(module_name)/
shell.sugarlabs.org:/upload/sources/sucrose/fructose/ (module_name)/
which translates to:
which translates to:
http://download.sugarlabs.org/sources/sucrose/fructose/(module_name)/
http://download.sugarlabs.org/sources/sucrose/fructose/ (module_name)/
* Push the release tag to the project repository,
* 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.
git push --tags
* Upload the bundle to activities.sugarlabs.org, with a high level, user oriented list of changes, which will cause a release mail to be sent to sugar-devel@lists.sugarlabs.org.
=== Using the release script ===
=== Using the release script ===
For both, fructose and glucose components you can use the release script in [http://git.sugarlabs.org/projects/sugar-tools sugar-tools] to do the above tasks in one go.
For both, fructose and glucose components you can use the release script in [https://github.com/sugarlabs/sugar-tools sugar-tools] to do the above tasks in one go.
You can check out the available commands (Note, the script does try to release the software of the directory you are currently in):
You can check out the available commands (Note, the script does try to release the software of the directory you are currently in):
* Ensure that all the module releases are available by the scheduled date.
* 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.
* Run automatic and manual QA on the releases.
* 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-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 references to each source module and a global list of changes.
=== Roadmap Update ===
=== 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:
The Development Team's [[{{Upcoming Stable Release}}/Roadmap|Roadmap]] is updated at the beginning of each release cycle by the release team. It may include:
* Detailed schedule of release dates and freeze points.
* Detailed schedule of release dates and freeze points.
=== Feature freeze ===
=== Feature freeze ===
When a Feature Freeze is scheduled, all new features have to be complete, reviewed and pushed to the repository. "Feature" should be interpreted as "Functionality" or "Ability". Bug fixes of existing features are not affected.
This allows developers to concentrate on refining the new features instead of adding yet more functionality.
This allows developers to concentrate on refining the new features instead of adding yet more functionality.
=== UI Freeze ===
=== UI Freeze ===
When a UI Freeze is scheduled, major UI revisions or changes must be done before this date.
This encourages developers to focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated.
This encourages developers to focus on stability and bug-fixing rather than UI changes. At this point, documentation writers do not have to worry that their work will become outdated.
=== String cooling===
=== String cooling===
When a string freeze is scheduled, 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===
When a string freeze is scheduled, after the scheduleddate 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 ===
When a stabilizing phase is scheduled, 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 a 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 may 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.
A new branch is created on the Pootle server, e.g., Fructose-0.96 and Fructose-0.98. The Localization team (the coordinator of a translation team) may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches as well.
A new branch is created on the Pootle server, e.g., Fructose-0.96 and Fructose-0.98. The Localization team (the coordinator of a translation team) may push translations to any or all of the corresponding branches of your project. Changes to your master branch are not necessarily intended for the release branches as well.