Molle Bestefich wrote:
> SteveKing wrote:
>> Molle Bestefich wrote:
>>> A RC would be a big improvement.
>>> You should take on a different look at the RC concept, I think.
>>>
>>> The RC is like saying that you think that this particular nightly
>>> is a very good nightly.
>>> If enough people agree (well, rather, if the amount of people that
>>> disagree are small enough), that *exact* binary is released as the
>>> final version.
>>
>> Well, as I already mentioned: the docs and the translations of the
>> docs aren't finished yet. So I *can't* make such an RC release.
>
> In that case, I think you're pushing the release over the counter far
> too fast.
It's not fast at all. The nightly builds have been edging us closer to
the release for weeks. But we do actually have a documented release
procedure, and it is in trunk/release_procedure.txt.
>>> It is a message to people that they should test it better than they
>>> do a nightly, and it is a very, very good thing to do before
>>> releasing...
>>
>> If we do an 'official' RC, that means updating the website, writing
>> announcements, ... - a lot of work for us (me).
No, we switch the nightly to a stable release candidate, according to
our procedure.
>> Also, people who don't
>> use the nightly builds usually also don't report bugs that fast as it
>> would be required for the RC (after all, we want release the final
>> version on june 1st).
See above. I think there has been more interest in the nightlies because
it is a long time since the last feature release (as opposed to the
bugfix releases).
> June 1st seems way too close for comfort, if you ask me.
> Subversion has a four week soak period where no new features are
> allowed, how about following that lead? Or just 2 weeks?
We don't have to follow Subversion on this one. Subversion is reponsible
for data safety and they have to be ultra-cautious in their releases.
TSVN just provides a GUI front end and uses the SVN library to control
the user's data. If we get it wrong, usually it just means something is
in the wrong place, or doesn't quite do what you expect, but we have to
try very hard to cause any serious inconvenience.
> I still think a RC should be announced, to tell people that they have
> a chance to test the binary that will become the final.
I think an RC would be a good plan, but get concensus before branching
because we know there is some catching up to do in the German & Spanish
docs, and it will be a pain to do lots of merging.
Regardless of whether or not we do an RC, the nightly build should
switch from the SVN 1.2 branch to the 1.2.0 tag as soon as it is
released.
Simon
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon May 23 19:08:26 2005