kfogel@tigris.org writes:
> * notes/releases.txt: Renamed from tarball_release_procedure.txt.
> Update to reflect the new release process. Michael, let me know if
> anything is missing or inaccurate.
>
> +4. Run './dist.sh [ARGS ...]' (see dist.sh for details about ARGS)
> + Watch dist.sh's output to make sure everything goes smoothly; when
> + it's done, you'll have 'subversion-BLAH.tar.gz' in the cwd.
dist.sh requires a configured source tree so that you have a
Makefile. If this was mentioned anywhere then I missed it. However, its
probably not worth mentioning in either case as if you don't have the
Makefile then building the docs will fail and you'll see that in the
script's output.
Also, I had to add some -Xmx options to the java command in fop.sh as my
JVM was running out of memory generating the ps/pdf files.
> + g) subversion/clients/cmdline/svn co http://svn.collab.net/repos/svn/trunk
> + h) rm -rf trunk
> + i) subversion/clients/cmdline/svn co svn://svn.collab.net/repos/svn/trunk
I didn't even know svn.collab.net was running svnserve.
> +8. Move branch into the tags directory in the repository. Now that
> + the release is public, no more changes can happen on that branch.
> + If we discover problems with the release, then we make a new branch
> + (with the minor version number incremented), apply fixes, and go
> + through the release process again.
> +
> +9. Update status webpage (on trunk and branch).
If you've already done step 8 then you can't do step 9.
> +10. Post news item, send announcement to dev and announce lists.
I didn't know the format of the release announcement so I just winged it.
> +11. If necessary, post newest versions of docs to web sites.
A coworker mentioned to me that if it weren't for my daily ravings about
how wonderful subversion it then he would never have heard of it. Should
be me "advertising more" than we are?
Michael Price Member of the Engineering Staff
Distributed Processing Lab; Lockheed Martin Adv. Tech. Labs
A&E 3W; 1 Federal Street; Camden, NJ 08102
856-338-4021, fax 856-338-4144 email: mprice@atl.lmco.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Feb 20 18:39:39 2003