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

Re: When to tag was Re: Soliciting signatures for Subversion 1.1.4

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2005-04-03 02:27:05 CEST

--On Sunday, April 3, 2005 1:15 AM +0100 Max Bowsher <maxb@ukf.net> wrote:

> HOWEVER, I do think that tarballs should NOT appear at
> http://subversion.tigris.org/tarballs/ until after they are official.

I agree. For httpd releases, they usually appear under:

<http://httpd.apache.org/dev/dist/>

Then, when they are official, they go to:

<http://www.apache.org/dist/httpd/>

For SVN, perhaps:

<http://subversion.tigris.org/pre-release/>

But, I don't know how much control CES gives us to add things under the name
space. I'd prefer that any place doesn't require a committer to put up the
space: i.e. it should somehow be a part of the SVN infrastructure.

> I'm not entirely sure dev@svn is the right place to mention the existance of
> the waiting-for-test tarballs, but I can't think of anywhere better.

I would prefer that any list would be a public list. Doing this on a private
list is something I'd really prefer to avoid: the release process should be
transparent to everyone. I'd prefer to get as much feedback during this
'pre-release' time period as possible. If it's a dud, we would like to know
before we send the public announcement. =)

FWIW, httpd releases seeking approval go to dev@httpd, current-testers@httpd,
and stable-testers@httpd. Any beta releases only go to current-testers@httpd.
However, I think a new mailing list might be overkill for svn. -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 3 02:29:31 2005

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.