[FFmpeg-devel] [PATCH] version.sh: Always use latest tag for generated version number

Timo Rothenpieler timo at rothenpieler.org
Fri Mar 4 11:05:08 CET 2016

>> Of course, this argument operates on the premise that 
>> making things easier for users is of utmost concern 
>> for us. Please inspire me if this is not the case.
> On the contrary, I believe while the current versioing 
> scheme is simple and understandable, the suggested one 
> is misleading, both for users and when reading user 
> questions.

The current versioning scheme is indeed simple, but useless in almost
all other aspects.
It gives no indication about what release it is close to, so the
ChangeLog becomes useless without digging through the git log first.
It's also counter-intuitive, as people are used to regular version numbers.

Also, releases are also continuously numbered, so I don't see what's
better about the always increasing number based on some old tag.

Will resend the patch without the fetch part, but still, on all of my 3
dev machines i had to manually issue a fetch for the latest tags to show up.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20160304/2027f425/attachment.sig>

More information about the ffmpeg-devel mailing list