[FFmpeg-devel] [PATCH] Use git describe in version.sh

Ramiro Polla ramiro.polla
Fri Dec 31 02:46:29 CET 2010

On Thu, Dec 30, 2010 at 11:09 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
> On Thu, Dec 30, 2010 at 12:30:29AM +0000, Ramiro Polla wrote:
>> On Mon, Dec 27, 2010 at 7:37 PM, Michael Niedermayer <michaelni at gmx.at> wrote:
>> > On Mon, Dec 27, 2010 at 07:34:43PM +0100, Reinhard Tartler wrote:
>> >> For releases, how about something like "0.7-12-githash", where "0.7"
>> >> stands for branchpoint for the 0.7 release, and "12" indicates twelve
>> >> additional commits from there. To avoid confusion, we name the first
>> >> 'real' release then "0.7.0", such that real releases always end up with
>> >> three parts in the version number.
>> >
>> > I dont care at all how relese branches are named but i do NOT want release
>> > nonsense to leak into the main development revissions
>> > devel HEAD is not a continuation of the last release. The last release is a
>> > possibly modified branch of devel HEAD.
>> > Releases can be done of revissions long after they are pushed to the public,
>> IMO tagging after branching and having "0.7-12-githash" would be good.
> IMO having tags in trunk where branches where made, makes sense, but refering
> to main devel as a <last release>-whatever num is silly
> Our development model is not even remotely matching this
> we dont focus primarely on releases and then after each release focus on
> the next.

I might not have made myself very clear but I meant the release
branches being tagged, not the master branch.

More information about the ffmpeg-devel mailing list