> On Oct 25, 2017, at 7:48 AM, Eric Covener wrote:
>
>> The guidelines are fine with me and seem to make sense to get to an API
>> stable next GA. It is good to have a list of 'To Do's' that needs to be done
>> before next GA. That helps people looking for interesting and
> The guidelines are fine with me and seem to make sense to get to an API
> stable next GA. It is good to have a list of 'To Do's' that needs to be done
> before next GA. That helps people looking for interesting and useful work to
> spend their time :-).
> Once it is decided that the API is
> -Ursprüngliche Nachricht-
> Von: William A Rowe Jr [mailto:wr...@rowe-clan.net]
> Gesendet: Dienstag, 24. Oktober 2017 19:00
> An: httpd <dev@httpd.apache.org>
> Betreff: [Proposal] 2.5.x -> 2.6.0/3.0.0 transition guidelines
>
> I'd like to propose t
I'd like to propose the following, so we can decide on what course to
chart between here and there.
Today we are at 2.5.0-dev, slated to become 2.5.0 non-GA release.
Through a series of non-GA releases, 2.5.x is eventually approved to
become the next 'evens' GA release. What we number that by