This is the mail archive of the
mailing list for the binutils project.
Re: Release 2.23 ?
See point 4. If you tagged the wrong thing as 2.23, then you need to
do one of two things:
1) Ship the wrong thing. This seems unproductive.
2) Re-release with a new number and ship the right thing.
3) Bonus option. Don't announce it, include more test suite changes,
and any fixes required to make them pass, and then release a new
version and ship a better thing.
Shipping something that isn't tagged as an official version, when
something else is tagged as that version, would be an eye-popping
thing to do, especially in such an important project.
On Wed, Oct 24, 2012 at 9:50 AM, Tristan Gingold <email@example.com> wrote:
> On Oct 24, 2012, at 7:58 AM, Ralf Corsepius wrote:
>> On 10/23/2012 01:39 PM, Tristan Gingold wrote:
>>> On Oct 23, 2012, at 10:40 AM, Ralf Corsepius wrote:
>>>> On 10/23/2012 10:27 AM, Andreas Schwab wrote:
>>>>> Tristan Gingold <firstname.lastname@example.org> writes:
>>>>>> Humm, is there any easy way to fix that ? I cannot find one.
>>>>> Any attempt at correcting it would require rewriting history and
>>>>> probably makes things only worse.
>>>> Agreed ... release a correctly tagged 2.23.0 instead and forget 2.23 has ever exited?
>>> x.y.0 are in fact never released.
>> Well, the rationale escapes me, but I don't have to understand everything. ;)
> I suppose it avoids the confusion with x.y
>> Anyway, there is still the possibility of releasing a 2.23.1.
> I don't think this is worth, but it is a strong argument for making a 2.23.1 release later.