Re: Current state of release planning.

[David Kastrup]

John Mandereau <address@hidden> writes:

> Le dimanche 12 août 2012 à 14:16 +0100, Graham Percival a écrit :
>> Actually, there's an unforseen problem: the website can only
>> advertise VERSION_STABLE and VERSION_DEVEL.  STABLE is obviously
>> 2.14.2 until 2.16.0 is out.  If we want testing for the
>> pre-releases (which we obviously do), then VERSION_DEVEL must be
>> 2.15.95 (or whatever number you call it).  Ergo, no 2.17.0
>> releases.
>> 
>> Changing this would require a fair amount of hacking on the
>> website build process and documentation; not impossible, but not a
>> fun task either.
>
> Do we want to keep 2.14 downloads visible for some time, say, one or two
> months, after 2.16.0 is out?

No.  It does not play nice with GCC 4.6.0, 4.6.1, 4.6.2, and 4.7.0.  The
GPL demands that we offer source downloads along with any binaries, and
we are just asking for trouble in that manner.

The situation might be somewhat different with 2.18, but the sooner we
can declare 2.14 off the charts, the better we are off.

> because I'd like to submit fixes for issues 2366 and 2529 and get them
> committed in stable/2.16 branch.

2366 (update THANKS) is obviously ok.  2529 (configure errors out for
non-existent software) only for very well-confined changes.  I don't
want any last-minute errors.

-- 
David Kastrup