Changes

<noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>

<noinclude>{{TeamHeader|Development Team|roadmap_link={{Upcoming Stable Release}}/Roadmap}}</noinclude>

== Goals and modules proposal ==

== Goals and modules proposal ==

More in detail:

More in detail:

=== Glucose ===

=== <abbr title="Glucose, the base Sugar environment">Glucose</abbr> (base) modules===

* Build a source tarball  

* Build a source tarball  

   

   

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

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

=== Fructose ===

===<abbr title="Fructose, the base set of demonstration activities">Fructose</abbr> (base activity) modules===

* Build a source tarball

* Build a source tarball

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.

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.

== Sugar release cycle==

== Sugar release cycle==

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:

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:

  git checkout -b sucrose-0.84 origin/sucrose-0.84

  git checkout -b sucrose-0.84 origin/sucrose-0.84

  git pull

  git pull

== Bug triaging ==

== Bug triaging ==

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.

==Subpages==

==Related pages==

{{Special:PrefixIndex/{{PAGENAME}}/}}

{{Template:Platform Cycle Linkbar}}

See [[:Category:Release Notes]]

 

[[Category:Development Team/Release]]

See also [[:Category:Release Notes]]{{Special:PrefixIndex/{{PAGENAME}}/}}