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

Safety first: previewing with a 1.0.0-beta1

From: <kfogel_at_collab.net>
Date: 2004-02-17 21:23:32 CET

Jostein, would you be up for rolling a subversion-1.0.0-beta1.tar.gz
on Friday, if we get all the pending tweaks in by the end of Thursday?

This way we'd have a couple of days to sanity check 1.0.0-beta1,
knowing that it's (almost) exactly the same as 1.0.0. On Monday, we
can release 1.0.0 with a bit more assurance :-).

Fitz and others have pointed out the Goodness of a "one last check"
tarball, just to make sure we haven't done anything dumb. The
difference between '1.0.0-beta1' and '1.0.0' would be *only* the tweak
in svn_version.h, changing SVN_VER_TAG from "beta1" back to "".

I realize that we haven't yet completely worked out the exact
mechanics by which we'll represent the release suffixes "-beta1",
"-beta2", etc. So this time, some small hand-tweaking might be
necessary. Fortunately, it looks like dist.sh is already equipped to
generate releases named "1.0.0-beta1", e.g.,

  $ ./dist.sh -v 1.0.0-beta1 ...

The only other thing we need to ensure is that the client itself
prints out a distinguishing version:

   $ svn --version
      svn, version 1.0.0 (beta1)

... which is what the SVN_VER_TAG hack mentioned above should (?) do.

Let us know if you're okay with this.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 17 22:25:48 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.