>From http://scons.org/wiki/SconsMercurialWorkflows#Guidelines
> The main repository is at https://bitbucket.org/scons/scons .You will need to > create a free account at Bitbucket. > "Default" branch is where current development is done; branches are for fixes > to existing releases. It is better to leave named branches for big features or else they have a habit of cluttering Bitbucket interface. Pull request are lightweight anonymous branches that together with issue reference should give a pretty usable history. > Anyone can fork the repo on the Bitbucket site, clone it on their own > computer and make modifications. It is better to clone official repo, then fork and upload changes to the fork. This way `hg out` command will show difference between local and remote, and 'hg inc' inspect new changes. > If you have a patch which follows the submission guidelines (code, doc, test) > you can submit a pull request at bitbucket. > Patches are reviewed and accepted by the release team. Pull requests? > For point releases and fixes, apply the patch to the oldest supported release > and merge forward always. > Never merge the trunk into a release branch, or you'll get everything. Trunk? ) -- anatoly t. _______________________________________________ Scons-dev mailing list Scons-dev@scons.org http://two.pairlist.net/mailman/listinfo/scons-dev
