Hey, for the guys of us who want to do BitBake releases. Here is a sketch of what I follow when doing a release. I have a local checkout of branches, tags and trunk to ease the copying
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 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 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. 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). z. PS: richard you are a project admin so you can do releases. _______________________________________________ Bitbake-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/bitbake-dev
