Ben wrote:
> On Feb 20, 2005, at 12:26 AM, Justin Erenkrantz wrote:
>>
>> The initial stabs at this documentation are in notes/releases.txt, but
>> without
>> any other RMs having done a release recently, we need to test the
>> procedures.
>>
>
> Ahem... notes/releases.txt isn't a rough outline or "initial stab".
> It's gone through dozens and dozens of rewrites over N years. It's the
> result of continuous refinement at the hands of different RMs. And Ben
> Reser has refined that document more than anyone else. Take a look at
> it... it's well-written enough that really any committer can follow the
> procedures. And indeed -- excluding 'make check' -- it takes Ben less
> than 30 minutes to do it.
Based on my reading of notes/releases.txt, there are a number of implicit
things that must be understood in order to do a release. That document
isn't enough on its own for anyone to do a release that we'd consider
'good'.
It doesn't describe how to create a release from a branch - only from
trunk. Nor, does it describe our current policy for summarizing CHANGES
entries as we now want the RM to do it.
Where does it say what are the 'good' versions of autoconf or libtool?
Currently, dist.sh or buildcheck.sh don't enforce that - and that's
badness, IMHO.
It also doesn't describe how to create the .zip CRLF source files - which
is something we've been intending to do since 1.1 came out - although
dist.sh seems to have the required bits to do this, but it isn't
documented.
These are only some of the things I intend to address. And, by having
someone go through the release process who hasn't done it before (or
recently) with an eye on getting these docs right, I think we'll end up
with a far better document that'll be closer to our ideal. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 21 19:12:02 2005