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

Re: 1.0.0, 1.0.x plan

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-01-27 20:27:50 CET

Jostein Chr. Andersen wrote:

>On Monday 26 January 2004 17.59, kfogel@collab.net wrote:
>>I think the above categories don't even need voting, let's just treat
>>them like trunk commits, with post-facto review. Meanwhile, the
>>categories below would use the voting system, but still not affect the
>>soak time:
>> * Anything in tools/, packages/.
>The packages too? I have used the installer source from the trunk all the
>time (while the branched code have been older and older).
>The only win32 installer code that works is that one in the trunk (it's
>even the most stable installer so far :-).
This is not a good situation. IMHO the installer on the branch should be
kept up-to-date -- remember, Win32 build on the trunk is already
significantly different than the one on the branch (trunk uses APR DLLs)

>So let's branch from the 0.37.0 tag and make a new STATUS file so I can
>write an item there as soon as possible (I do even have more changes to
>do there before 1.0).
I disagree; simply merge from tags/0.37.0 to branches/1.0.x.

>Please, remember that packages/installers are made _after_ the tarball.
>Changes in this might occure after a release tag.
I really don't know why this is necessary. All necessary changes to
installers should be made on the release branch before the release is
tagged, otherwise people can't make their own packages from the tarball.
That's weird.

We can do this at least for Windows, where the package maintainer and
release manager are the same person. :-)

Brane Čibej   <brane_at_xbc.nu>   http://www.xbc.nu/brane/
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 27 20:28:39 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.