Re: SVN snapshot versioning
Florent Rougon <firstname.lastname@example.org> writes:
> Sorry, not at all. Besides what Martin explained, using 2.1 in your
> version number without knowing for sure that 2.1 is going to be the next
> release is ugly, even if it were harmless (which is not the case).
> Better use something you do know: if this SVN snapshot is based on 2.0,
> then use 2.0.
Yes, you should pick the form of the version number based on your
knowledge, or lack of knowledge, about what the next version will be.
Usually this is fairly straightforward if you're following upstream
If upstream just released 2.0 and has since committed more patches, so you
want to package a snapshot, then call it 2.0+svn-rNNN or by date or
whatever you prefer.
If upstream is preparing 2.1 and you're packaging a snapshot of what is or
will be the release branch, then use 2.1~svn-rNNN.
In other words, use <previous-version>+<svn-stuff> if you're packaging
that version plus some additional upstream modifications, and use
<next-version>+<svn-stuff> if you're packaging an alpha or beta arelease
In practice, this is almost never ambiguous. In the few cases where
upstream manages to make themselves and everyone else horribly confused,
well, that's what epochs are for.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>