Hi, I also think we should expedite this, so we have a 3.x free version by the end of this year. btw, are there any 3.x usages in Oak?
WDYT? regards, toby On Thu, Oct 27, 2016 at 3:08 AM, Julian Reschke <[email protected]> wrote: > On 2016-10-26 17:28, Roy T. Fielding wrote: > >> On Oct 26, 2016, at 6:13 AM, Julian Reschke <[email protected]> wrote: >>> >>> Hi there, >>> >>> context: <https://issues.apache.org/jira/browse/JCR-2406> >>> >>> Summary: we want to get rid of our dependency of httpclient 3.* (< >>> http://hc.apache.org/httpclient-3.x/>), which as been end-of-lifed >>> quite some time ago. >>> >>> This will affect our public API, which extends classes from it. >>> >>> The current plan is to add a new set of APIs (probably based on >>> HttpClient 4.5.x) in the next stable Jackrabbit release 2.14, planned to be >>> released in Spring 2017. At that point, we'll also deprecate the old >>> classes. >>> >>> Later on, we would *remove* the httpclient 3.x dependency and the old >>> classes -- the plan would be to do that in the subsequent stable release: >>> Jackrabbit 2.16, which could come out in Spring 2018. >>> >>> At that point, users of the old API can: >>> >>> - either continue using Jackrabbit 2.14.*, or >>> >>> - update their own code to work with Jackrabbit 2.16.*. >>> >>> Feedback appreciated -- either here, or in < >>> https://issues.apache.org/jira/browse/JCR-2406>. >>> >>> Best regards, Julian >>> >> >> That seems like an awful long time. Assuming no one objects to the need >> to update, >> I suggest that the timeline should take care of itself. IOW, if someone >> commits an >> updated API then it can be released "in the next release", after which >> the old API >> can be removed and 2.16.0 considered for the next release. >> >> That can all be done next week, if anyone gets excited. ;-) >> >> ....Roy >> > > I'm all for speed. > > Just to be clear: 2.16 is the "next" release after 2.14 (we use odd > numbers for the cuts from trunk as unstable releases). > > Best regards, Julian > >
