[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 4988 - in trunk: . notes

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2003-02-20 18:17:43 CET

Michael Price <mprice@atl.lmco.com> writes:
> > +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.

It's probably worth mentioning, to save time if nothing else.

> 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.

This should probably be mentioned in docs/book/README. Can you say
exactly what you did, so I can document it accurately?

> > + 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.

Oops. It's not, my fault. Steps (i) and (j) should go.

> > +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.

Good point. Updating the status page for the dist isn't so important,
it's mainly important that it be up to date in trunk.

I'll fix all the above stuff. If you see any more, feel free to fix
them yourself in trunk (in general, if it's about releasing, it's
yours to tweak as needed).

> > +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.

It was perfect!

> > +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?

Not as part of the release process, at any rate.

As we get closer to 1.0, Slashdot et al will start to take notice, and
we'll get the attention when we're prepared for it. Right now, we
mainly want to attract patient users who can take the time to file
thorough bug reports.


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:57:13 2003

This is an archived mail posted to the Subversion Dev mailing list.