607
edits
Changes
→Branching
At the beginning of each unstable development cycle, a branch is usually created to host development on the stable release. It should be done lazily, whenever unstable changes are ready to be committed on master. Please use name in the sucrose-XXX form (for example sucrose-0.82). Each module maintainer is responsible to inform the sugar@laptop.org and localization@laptop.org lists about the branch.
At the beginning of each unstable development cycle, a branch is usually created to host development on the stable release. It should be done lazily, whenever unstable changes are ready to be committed on master. Please use name in the sucrose-XXX form (for example sucrose-0.82). Each module maintainer is responsible to inform the sugar@laptop.org and localization@laptop.org lists about the branch.
You can create a remote branch like this:
{{{
git clone git+ssh://dev.laptop.org/git/sugar
cd sugar
git branch sucrose-0.82
git push origin sucrose-0.82
}}}
And to work on it:
{{{
git clone git+ssh://dev.laptop.org/git/sugar
git checkout --track -b sucrose-0.82 origin/sucrose-0.82
git pull
}}}
== Roadmap ==
== Roadmap ==