Re: milestone 9 -- testing before releasing

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

Greg Stein mentioned to me privately that there's a better way to do
this, and I agree: rather than impose so much overhead on each tarball
creation, we can just post tarballs whose descriptions qualify them as
"Needs testing", or "We expect this to work.", etc.

Note that this is same philosophy, different process. We're still
paying more attention to testing, and being more careful about calling
it a stable release. And we're still trying to get testing on as many
platforms in PORTING as possible (for that matter, we should platforms
as appropriate).

When it starts to stabilize, then we can branch and roll the last
tarball(s) out of the branch, if code flux in the trunk makes that a
sensible thing to do.

-K

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