apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From William A Rowe Jr <wr...@rowe-clan.net>
Subject Re: 1.6 apr/apr-util scope/timetable?
Date Fri, 02 Dec 2016 17:36:15 GMT
On Wed, Nov 30, 2016 at 11:23 PM, William A Rowe Jr <wrowe@rowe-clan.net>
wrote:

> Even as httpd is operating under paralysis by analysis, we are long past a
> year since the last releases.
>
> Is there anything holding up the jumps to 1.6, or 2.0?
>
> I'd personally like to see an API harmonising memcache to redis, but that
> can't possibly be a showstopper to any incremental release.
>

https://bz.apache.org/bugzilla/show_bug.cgi?id=42848 (IP TOS) looks
like a good enhancement before we tag 1.6. Anything else lingering?


> If nobody else offers, I'll T&R 1.6 objects in 72 or so hours for a vote,
> alongside the first 2.0 RC.
>
>
Since we have some positive activity on this thread, I'm going to put
off a T&R into sometime next week, to give us a chance to pick these
things up. Please update STATUS in apr / apr-util 1.6 branches with
any low-hanging fruit over the weekend so I don't miss it.

I can't think of a way to tag an intermediate, 1.9.x won't work by our
versioning rules, so I'm tempted to call it 2.0.0-dev-rc1 (with the intent
to have a number of -rcX tags before we bless 2.0.0-stable). Another
idea would be to use 2.0.X as 'unstable' (always -dev) and have our
first stable-GA ready release as 2.1.0. Thoughts?

Mime
View raw message