Start by making sure everything is OK.
-1. svn co https://svn.sourceforge.net/svnroot/check
-2. cd check/trunk (or tagged version)
-3. autoreconf --install
-4. ./configure
-5. make check
-6. ulimit -c 0
-7. make distcheck
-8. make -C doc check.html
-
-When the above works:
-
-1. Decide on revision suitable for release.
-2. svn cp -rXXX https://svn.sourceforge.net/svnroot/check/trunk https://svn.sourceforge.net/svnroot/check/tags/check-X.Y.Z
-3. cd ~/check
-4. svn up
-5. cd check-X.Y.Z
-6. Update NEWS with info from `svn log | less`.
-7. Update TODO and make sure version numbers match appropriately.
-8. Update configure.ac with new version numbers.
-9. svn ci
-10. autoreconf --install
-11. ./configure
-12. ulimit -c 0
-13. make check
-14. make distcheck
-15. make -C doc check.html
-16. rsync -av . USERNAME@shell.sourceforge.net:/home/groups/c/ch/check/htdocs
-17. sftp USERNAME@frs.sourceforge.net
-> cd uploads
-> put check-X.Y.Z.tar.gz
-> exit
-18. Locally copy NEWS to NEWS-release, cut out old release news.
-19. Copy SVNChangeLog to SVNChangeLog-release, cut out old release log.
-20. Go to: http://sourceforge.net/project/admin/newrelease.php?package_id=20116&group_id=28255
-21. Enter X.Y.Z as new release name, hit "Create this release"
-22. Upload NEWS-release, SVNChangeLog-release
-23. Tick "Preserve my pre-formatted text", hit "Submit/Refresh"
-24. Tick "check-X.Y.Z.tar.gz" in list, hit "Add Files and/or Refresh View"
-25. Choose "Platform-Independent" for Processor
-26. Choose "Source .gz" for File Type
-27. Hit "Update/Refresh"
-28. In a new tab or window go to: http://sourceforge.net/project/showfiles.php?group_id=28255
-29. Check project notes, verify NEWS-release and SVNChangeLog-release uploads look OK.
-30. Back in the old tab, tick "I'm sure" and hit "Send Notice".
-31. Send the following email to check-devel at lists dot sourceforge dot net:
+Start in a configured trunk.
+
+1. Decide on a X.Y.Z revision suitable for release.
+2. make SF_USERNAME=username RELEASE_VERSION=X.Y.Z preparerelease
+ This will tag trunk as https://svn.sourceforge.net/svnroot/check/tags/check-X.Y.Z
+3. Follow the prompts
+4. Use the following template to announce the release:
+=====
Subject: check-X.Y.Z released
Hi,
<some sentence about the release, e.g. "This is a bug fix release.">
Please test it out and report any problems you might have!
-http://prdownloads.sourceforge.net/check/check-0.9.5.tar.gz?download
+http://prdownloads.sourceforge.net/check/check-X.Y.Z.tar.gz?download
Thanks,
`whoami`
<paste contents of NEWS-release here>
-32. Send the same message to check-announce and check-users
-33. cd ~/check/trunk
-34. svn up
-35. svn merge -r(rev. in step #4):(rev. in step #9) ../tags/check-X.Y.Z .
-36. svn resolve any conflicts, check everything looks fine.
-37. svn ci
+=====
+5. Follow the remaining prompts.
fi
ACLOCAL_AMFLAGS = -I m4
+
+doc/check.html:
+ $(MAKE) -C doc check.html
+
+# check we can do a clean build, including docs.
+# perhaps we should check for out of date (svn st -u) and modified files.
+prereleasecheck: doc/check.html
+ -$(MAKE) distclean
+ ./autoreconf -i && ./configure \
+ && ulimit -c 0 && \
+ $(MAKE) distcheck
+
+RELEASE_VERSION ?= unset
+SF_USERNAME ?= unset
+SVN_REVNO = `svn st -u | grep "Status against revision:" | awk '{ print $4 }'`
+releasevars:
+ @if [ "unset" = "${RELEASE_VERSION}" ]; then \
+ echo "set RELEASE_VERSION to something like 0.9.6 to prepare a release."; \
+ false; \
+ fi
+ @if [ "unset" = "${SF_USERNAME}" ]; then \
+ echo "set SF_USERNAME to your sourceforge username"; \
+ false; \
+ fi
+
+preparerelease: releasevars prereleasecheck
+ -# check we have can connect properly to do release tasks before tagging:
+ sftp -b /dev/null ${SF_USERNAME}@web.sourceforge.net
+ sftp -b /dev/null ${SF_USERNAME}@frs.sourceforge.net
+ svn cp -rXXX https://svn.sourceforge.net/svnroot/check/trunk https://svn.sourceforge.net/svnroot/check/tags/check-${RELEASE_VERSION}
+ svn co https://svn.sourceforge.net/svnroot/check/tags/check-${RELEASE_VERSION} check-${RELEASE_VERSION}
+ @echo "You need to:"
+ @echo "Update NEWS with info from `svn log | less`."
+ @echo "Update TODO and make sure version numbers match appropriately."
+ @echo "Update configure.ac with new version numbers."
+ @echo "Then svn commit these changes."
+ @echo "CTRL-D when finished or 'exit 1' to abort."
+ @echo "aborting will leave the partially prepared release in" `pwd`
+ cd check-${RELEASE_VERSION} && ${SHELL}
+ $(MAKE) -C check-${RELEASE_VERSION} dorelease
+ -svn merge -r${SVN_REVNO}:`svn st -u check-${RELEASE_VERSION} | grep "Status against revision:" | awk '{ print $4 }'` ../tags/check-${RELEASE_VERSION} .
+ @echo "Please resolve any conflicts"
+ ${SHELL}
+ svn ci -m "Merge back release ${RELEASE_VERSION}"
+
+
+dorelease: releasevars doc/check.html prereleasecheck
+ cp NEWS NEWS-${RELEASE_VERSION}.txt
+ @echo "You need to:"
+ @echo "cut out old release news from NEWS-${RELEASE_VERSION}.txt."
+ @echo "Add anything important from SVNChangeLog to NEWS-release."
+ @echo "CTRL-D to complete, or exit 1 to abort."
+ ${SHELL}
+ @echo uploading...
+ rsync -e ssh NEWS-${RELEASE_VERSION}.txt ${SF_USERNAME},check@frs.sourceforge.net:/home/frs/project/c/ch/check/check/${RELEASE_VERSION}/
+ rsync -e ssh check-${RELEASE_VERSION}.tar.gz ${SF_USERNAME},check@frs.sourceforge.net:/home/frs/project/c/ch/check/check/${RELEASE_VERSION}/
+ rsync -av doc/. ${SF_USERNAME},check@web.sourceforge.net:/home/groups/c/ch/check/htdocs
+ @echo "visit https://sourceforge.net/project/admin/explorer.php?group_id=28255"
+ @echo "Mark the NEWS file in check/${RELEASE_VERSION} as being a release note."
+ @echo "And the tar.gz file as being 'all platforms', using the NEWS file for release notes."
+ @echo "visit https://sourceforge.net/projects/check/files/"
+ @echo "Check it looks ok. It may take 15 minutes to show up."
+ @echo Finally, mail check-devel ,announce and users at lists dot sourceforge dot net
+ @echo an email (template is in HACKING) about this announcement.
+ @echo NEWS-release can be found at `pwd`/NEWS-release
+ @echo Note that with the tarballs, docs amd NEWS up, the release is done :P
+ @echo so you'll have to manuall roll back if you abort.
+ @echo "CTRL-D to complete, or exit 1 to abort."
+ ${SHELL}
+
+
+.PHONY: releasevars prereleasecheck preparerelease dorelease
projects / check / commitdiff