On Wed, 2007-03-14 at 12:59 +0100, Holger Freyther wrote: > 0. Make sure svn st and svn di don't show any changes, commit them or > revert > 1. Update the ChangeLog in trunk/bitbake or the branch (koen knows a > script for that, or grep through the log) > 2. check that ./setup.py dist create a tarball with the new needed > files, e.g. compare it with the result of svn export
"./setup.py sdist" > 3. Copy the trunk/bitbake to branch/bitbake-X.Y > 4. Copy the branch/bitbake-X.Y to tags/bitbake-X.YZ. > 5. change the version in bin/bitbake and in lib/bb/__init__py (do > that in branch, tags and even in trunk) to make clear which source is > used. > 6. svn st | wc -l and check that it is 2* the branches/tags/trunk you > have touched > 7. svn di and check the version is correct > 8. Create a new ChangeLog entry for the branch and trunk with the new > version number > 9. svn ci > 10. ./setup.py dist in the tags directory and extract a tarball "./setup.py sdist" > 10a. run the imaginary test-suite > 11. ftp ftp.berlios.de change to incoming and upload your tarball > 12. go to developer.berlios.de/projects/bitbake and add a release. No > worry you can always edit the site and recover any damage. Or just upload using their webform. We should consider switching to bz2 compression as they're removed .gz from the list of options. > 13. Check that version number, source type, etc. on the download page > is correct > 14. mail bitbake-dev and other lists about the release and write down > how great it is and that RP rocks (if you happen to be RP and feel > unconfortable claiming this you might skip it). 15. Hope svn doesn't break and you have to start again... I mention the above for the archives. Thanks for the instructions, they helped :) Cheers, Richard _______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
