Hello, Why are there different version numbers and different release cycles for otherwise interdependant artifacts? It's not always obvious which versions are compatible with each other.
In the same way that you don't need to wait for a change in every package of one of the current artifacts before releasing a new version of a subproject, I don't see any harm in having a single "Apache HTTP Client" project with all of the current deliverables as part of it (core, client, mime, etc). It would be simpler from my perspective (I don't know if my view is shared with others); using feature branches would avoid having to defer releases due to incomplete work-in-progress, so I don't see any disadvantages. Just a thought... -- Christopher On 6 June 2015 at 12:32, Oleg Kalnichevski <ol...@apache.org> wrote: > On Fri, 2015-06-05 at 10:52 -0600, Shawn Heisey wrote: > > On 6/5/2015 3:24 AM, Oleg Kalnichevski wrote: > > > The Apache HttpComponents project is pleased to announce 4.5 GA release > > > of HttpComponents HttpClient. > > > > > > HttpClient 4.5 (GA) is a minor feature release that includes several > > > incremental enhancements to the existing functionality such as support > > > for private domains in the Mozilla Public Suffix List. > > > > > > Users of HttpClient 4.x are advised to upgrade. > > > > Will there be any other components with a 4.5 release, or just the > > httpclient? I'm specifically interested in httpcore and httpmime. > > > > There unlikely to be any more feature releases in 4.x series of both > core and client. New features will be added to 5.0 only. There will > likely be bug fix releases in 4.x though. > > Cheers > > Oleg > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: httpclient-users-unsubscr...@hc.apache.org > For additional commands, e-mail: httpclient-users-h...@hc.apache.org > >
