On Fri, 2019-11-29 at 15:38 -0500, Gary Gregory wrote: > I think we should assume that we will keep binary compatibility. > > The next question is whether the new pooling code becomes the default > behavior or needs to be enabled. >
We have been keeping the 4.x codeline fully backward compatible for over a decade. I see no reason why we could not keep doing that a bit longer. However, I looked at how much effort and changes such backport would involve and I am pretty close to giving up on the whole idea. Oleg > Gary > > On Fri, Nov 29, 2019 at 3:31 PM Ryan Schmitt <[email protected]> > wrote: > > > Do you intend to remove the old connection pool implementations > > from 4.5.x, > > or just deprecate them? > > > > I would also like to echo Gary's question about binary > > compatibility, and > > what the compatibility implications are more generally for the > > client. > > > > On Tue, Nov 26, 2019 at 7:42 AM Oleg Kalnichevski <[email protected] > > > > > wrote: > > > > > Folks > > > > > > I would like to create new 4.5.x branch in HttpCore and do the > > > following > > > > > > * change its version to 4.5.0-alpha1 > > > > > > * change its JRE level from 1.6 to 1.7 > > > > > > * back-port new connection pool implementations from master to > > > that > > > branch > > > > > > * deprecate old connection pool implementations > > > > > > Would anyone have any objections to that? > > > > > > Obviously all new features would need to the 4.5.x branch and not > > > 4.4.x. The 4.4.x would be for critical bug fixes only. > > > > > > Oleg > > > > > > > > > --------------------------------------------------------------- > > > ------ > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
