Re: Next Release [was 'svnadmin load --parent-dir' seems to be a bit buggy]

Paul Lussier <pll@lanminds.com> writes:

> Version 0.26.0 (released 24 July 2003, revision XXXX, branches/release-0.26.0)
>
> Should XXXX be:
>
> a. 6523, the rev that the branch was created from ?
> b. some number in the future approximating when the release
> will actually be made ?
> c. something else?

        c. leave it out

If it is not clear what the revision represents then it is not
useful. I think a. would be OK if it was clear that this is what the
revision represents

   Version 0.26.0 (released 24 July 2003, branched from revision XXXX)
          

> I seem to recall someone (Philip?) mentioning that Michael Price used
> to 'guess'. I'm just not clear on what he based his guess on :)

As I understand it, Michael made the branch, committed any changes
required, and then as the final commit on the branch updated XXXX to
the revision of that final commit. This required him to 'guess' the
revision number of the final commit (as HEAD plus one), and it worked
provided HEAD didn't change while he was preparing or making the
commit.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org