Re: Current state of release planning.

[John Mandereau]

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?  If so, added support for advertising three
branches instead of the current two could be used for both that case
(stable, old, devel) and the current situation (stable-candidate,
stable, devel), with minor changes required to switch between the two.

If you think it's worth hacking this, I can switch to this, which would
mean delaying by one week setting Gerrit up on Grenouille and developing
Patchy to put results of patches tests on the web.  Yes, one week
because I'd like to submit fixes for issues 2366 and 2529 and get them
committed in stable/2.16 branch.

Best,
John