Once 5.0 is out we cannot break binary compatibility at all. That would be
for a 6.0 which would also require a package name change.

Gary

On Fri, Apr 5, 2019, 20:53 Ryan Schmitt <rschm...@pobox.com> wrote:

> I doubt I will; I'm completely overwhelmed with work right now. I mentioned
> the idea for completeness as something that would be nice to have, but it's
> not important enough to hold up an API freeze.
>
> Point of clarification: are we freezing the API for the entire 5.x line, or
> just 5.0.x? (I remember you mentioning that the 5.1.x series may include an
> upgrade to JDK8, but that's not quite the same thing as a breaking API
> change.)
>
> On Fri, Apr 5, 2019 at 2:30 PM Oleg Kalnichevski <ol...@apache.org> wrote:
>
> > On Fri, 2019-04-05 at 12:10 -0700, Ryan Schmitt wrote:
> > > I think I can live with AsyncDataConsumer as-is, now that the
> > > #consume
> > > returns void. Since it seems that initial buffering requirements are
> > > here
> > > to stay (as per our discussion in [1]), it would be nice to reify
> > > them in
> > > the interface somehow.
> > >
> >
> > Hi Ryan
> >
> > Do you have a particular time frame in mind you might get around to
> > doing that?
> >
> > Oleg
> >
> > > [1]
> > >
> >
> >
> https://github.com/apache/httpcomponents-core/pull/91#issuecomment-433901284
> > >
> > > On Thu, Apr 4, 2019 at 12:50 AM Oleg Kalnichevski <ol...@apache.org>
> > > wrote:
> > >
> > > > Folks
> > > >
> > > > I have a feeling that delaying 5.0 API freeze much longer does us
> > > > little good.
> > > >
> > > > There is a vast group of people who (regrettably) will not touch
> > > > anything with BETA in its release version. We are unlikely to get
> > > > more
> > > > feedback unless we start slapping GA on 5.0 releases.
> > > >
> > > > Is there anything realistically blocking us from freezing the 5.0
> > > > APIs?
> > > >
> > > > @Ryan
> > > >
> > > > Do you still intend to revise async data consumer and producer
> > > > APIs?
> > > >
> > > > Oleg
> > > >
> > > >
> > > > -----------------------------------------------------------------
> > > > ----
> > > > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
> > > > For additional commands, e-mail: dev-h...@hc.apache.org
> > > >
> > > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
> > For additional commands, e-mail: dev-h...@hc.apache.org
> >
> >
>

Reply via email to