Create a New Release
From Curuxa
This is a list of steps required to create a new release. Only the project leader is supposed to need this page.
- svn copy from trunk to branch directory
svn copy -m "creating release branch x.x.x" https://forja.rediris.es/svn/cusl4-curuxa/trunk https://forja.rediris.es/svn/cusl4-curuxa/branches/curuxa-x.x.x
- Update version and date (in branch)
- Make sure it compiles and runs properly
- Checkout changes on the branch
- svn copy from branch to tags directory
svn copy -m "tag release x.x.x" https://forja.rediris.es/svn/cusl4-curuxa/branches/curuxa-x.x.x https://forja.rediris.es/svn/cusl4-curuxa/tags/curuxa-x.x.x
- svn export curuxa to have a clean copy of the new version
svn export https://forja.rediris.es/svn/cusl4-curuxa/tags/curuxa-x.x.x curuxa-x.x.x
- Compile (Release)
- Test everything runs fine
- Tar-bzip2 and zip curuxa-x.x.x/ folder, removing any unnecessary extras (shouldn't be any). As some kind of "standard" in the GNU world, if the tar.bz2 is curuxa-x.x.tar.gz, the folder inside must be called curuxa-x.x
- Create standalone package
- Create Debian package
- Upload to package repository and test it
- Create Windows installer and test it
- Add a new file release in the File Release System
- Wait for mirrors to get synced, if needed
- Create a web page for the release
- Edit Downloads and versions on the website
- Edit "curuxa_latest" file in the website folder to update version for automatic version checking feature
- Add some news
- Update trunk version