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

Re: Release procedures improvements.

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-04-05 01:50:06 CEST

kfogel@collab.net writes:

> Philip Martin <philip@codematters.co.uk> writes:
>> > As the BSD guy points out, no matter how many warnings and danger signs
>> > we put up. If we post a tarball that is named like a official release
>> > tarball people are going to use it like that.
>>
>> Why does the test tarball need such a name?
>
> Philip, are you proposing that we give test tarballs a name like
>
> subversion-1.2.0-PRERELEASE.tar.gz
>
> or something like that, but which would unpack into subversion-1.2.0/
> and in every other respect look like the final tarball?
>
> No sarcasm intended, btw. I think this might be a great solution to
> the problem of doing things transparently while not prematurely
> releasing. I just want to make sure I understand the proposal.

Yes. The name need not contain 1.2 or even subversion, it's a very
short-term label after all, it doesn't need to be recognisable. The
tarball can be renamed when the RM decides to release it, all the
signtures should remain valid.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 5 01:52:11 2005

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