Section 0. should probably be rewritten, as git should make branching and merging much smoother.
Signed-off-by: Eino Keskitalo <evktalo@users.sourceforge.net>
S3CKMIO5JZKJI3P2ABDWEREKK66LKNT5ZCBVM3VRSKGWDMAU2JWQC
1. Branch trunk into the new version
svn cp https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/trunk
https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/branches/stone_soup-0.X
1. Branch master into the new version
git push origin origin:refs/heads/stone_soup.0.X
svn cp https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/branches/stone_soup-0.X
https://crawl-ref.svn.sourceforge.net/svnroot/crawl-ref/tags/stone_soup-0.X
In the branch you're about to tag:
git tag -a release-0.X.y
You'll need to push the tag into repository:
git push --tags
Do a clean checkout into a new folder, so you don't get any compilation
stuff into the distribution. Package the source (as described in 6.) and
build the binaries. If you want you can do some more sanity testing but it
shouldn't be necessary anymore.
You may want to make a new shallow clone into a new folder, to make sure you don't get any compilation stuff into the distribution.
Package the source (as described in 6.) and build the binaries. If you want
you can do some more sanity testing but it shouldn't be necessary anymore.