From 25b411f04feab88518cd1cacfb1cd6924990a271 Mon Sep 17 00:00:00 2001 From: cmpilato Date: Tue, 10 Apr 2007 15:37:13 +0000 Subject: [PATCH] Add some steps to releases.txt. git-svn-id: http://viewvc.tigris.org/svn/viewvc/trunk@1592 8cb11bc2-c004-0410-86c3-e597b4017df7 --- notes/releases.txt | 32 +++++++++++++++++++++----------- 1 file changed, 21 insertions(+), 11 deletions(-) diff --git a/notes/releases.txt b/notes/releases.txt index 08a28138..f79db648 100644 --- a/notes/releases.txt +++ b/notes/releases.txt @@ -24,52 +24,62 @@ numbers, and not literal): Commit any modifications. NOTE: This step should not be necessary for patch releases. -3. Update and commit the 'CHANGES' file. +3. Verify that copyright years are correct in both the license-1.html + file and the source code. -4. Test, test, test! There is no automatic testsuite available. So +4. Update and commit the 'CHANGES' file. + +5. Test, test, test! There is no automatic testsuite available. So just run with permuting different `viewvc.conf' settings... and pray. Fix what needs fixin', keeping the CHANGES file in sync with the branch. -5. At this point, the source code committed to the release branch +6. At this point, the source code committed to the release branch should exactly reflect what you wish to distribute and dub "the release". -6. Edit the file 'lib/viewvc.py' and remove the "-dev" suffix from +7. Edit the file 'lib/viewvc.py' and remove the "-dev" suffix from __version__. The remainder should be of the form "X.Y.Z", where X, Y, and Z are positive integers. Do NOT commit this change. -7. Update your working copy to HEAD, and tag the release: +8. Update your working copy to HEAD, and tag the release: svn update svn cp -m "Tag the X.Y.Z final release." . \ http://viewvc.tigris.org/svn/viewvc/tags/X.Y.Z -8. Go into an empty directory and run the 'make-release' script: +9. Go into an empty directory and run the 'make-release' script: tools/make-release viewvc-X.Y.Z X.Y.Z -9. Upload the created archive files (tar.gz and zip) into the Files +10. Verify the archive files: + + - do they have a LICENSE.html file? + - do they have necessary include documentation? + - do they *not* have unnecessary stuff? + - do they install and work correctly? + +11. Upload the created archive files (tar.gz and zip) into the Files and Documents section of the Tigris.org project, and modify the CHECKSUMS document there accordingly. Also, drop a copy of the archive files into the root directory of the viewvc.org website (unversioned). -10. Update the websites (both the viewvc.org/ and www/ ones) to refer +12. Update the websites (both the viewvc.org/ and www/ ones) to refer to the new release files. -11. Edit the file 'lib/viewvc.py' again, re-adding the "-dev" suffix +13. Edit the file 'lib/viewvc.py' again, re-adding the "-dev" suffix and incrementing the patch number assigned to the __version__ variable, and commit: svn ci -m "Begin a new release cycle." -12. Edit the Issue Tracker configuration options, adding a new Version +14. Edit the Issue Tracker configuration options, adding a new Version for the just-released one, and a new Milestone for the next patch (and possibly, minor or major) release. (For the Milestone sort key, use a packed integer XXYYZZ: 1.0.3 == 10003, 2.11.4 == 21104.) -13. Write an announcement explaining all the cool new features and +15. Write an announcement explaining all the cool new features and post it to the announce@ list, to the project's News area, and to other places interested in this sort of stuff, such as Freshmeat (http://www.freshmeat.net).