Re: [RFC] Poke releases, tags and branches

[Jose E. Marchesi]

> "Jose E. Marchesi" <jemarch@gnu.org> writes:
>
>> Hi people!
>>
>> I intend to use the following releasing schema.
>>
>> We will start with a pre-release 0.90.  It will most likely be followed
>> by several other pre-releases 0.91, 0.92, ... until we are happy with
>> it.
>>
>> At that point, we will release 1.0, then 1.1 and so on.  When we feel
>> that we have a candidate for poke 2.0, then we will release the
>> pre-release 1.90, followed by pre-releases until 3.0 is ready.
>>
>> And so on...
>>
>> In terms of git repo, we will have branches for the series:
>>
>>   releases/poke-0
>>   releases/poke-1
>>   releases/poke-2
>>   ...
>
> I would propose to call these maintenance/poke-$version for better
> differentiation from tag names.

I gave some thinking to this and I have to agree with you.  Using
releases/poke-N is definitely confusing :)

I will use maint/poke-1 for the 1.x maintenance branch and future
maintenance branches.

Thanks!