milestone 9 -- testing before releasing

In the past, we've had problems with release tarballs not working
right everywhere. Then we quickly fix the problems, and have to
re-roll a tarball, which is painful for users who downloaded the
previous tarball...

In other words, let's do some portability testing on this one
first, and *then* roll the tarball. :-)

I've created

   http://svn.collab.net/repos/svn/branches/

When Ben's finished with the "svn switch" work for ra_dav (he's just
finishing up now), we'll make

   http://svn.collab.net/repos/svn/branches/0.9/

and do all testing from that branch. As trunk bugfixes come in, we
can port them over. Yes, note that we can do merges even though we
don't have the "svn merge" command yet, it's just a little bit less
convenient, and we won't get the nice metadata that we'll have later
on. But that's not hugely important right now, and our log messages
will say enough that we can reconstruct the metadata later if we
really want to.

When that branch is known to compile and run on the platforms
mentioned in PORTING, plus any others people care to add, then we
release the tarball, and we'll have at least some reason to suspect it
of stability. :-)

I'll keep track of the administrivia for this, watch for uncovered
platforms in PORTING, etc.

-Karl

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:06 2006