On Sat, 2023-01-07 at 09:41 +0100, Michael Osipov wrote:
> Am 2023-01-07 um 09:16 schrieb Oleg Kalnichevski:
> > Please vote on releasing these packages as HttpCore 5.2.1.
> > The vote is open for the at least 72 hours, and only votes from
> > HttpComponents PMC members are binding. The vote passes if at least
> > three binding +1 votes are cast and there are more +1 than -1
> > votes.
> > 
> > Release notes:
> >  
> > https://dist.apache.org/repos/dist/dev/httpcomponents/httpcore-5.2.1-RC1/RELEASE_NOTES-5.2.x.txt
> > 
> > Maven artefacts:
> >  
> > https://repository.apache.org/content/repositories/orgapachehttpcomponents-1158/org/apache/httpcomponents/core5
> > 
> > Git Tag: 5.2.1-RC1
> >   https://github.com/apache/httpcomponents-core/tree/5.2.1-RC1
> > 
> > Packages:
> >  
> > https://dist.apache.org/repos/dist/dev/httpcomponents/httpcore-5.2.1-RC1
> >   revision 59182
> > 
> > Hashes:
> >  
> > 9cd57c54701ac40081894bcd35861a179780aa5ca4705187f680e2081b78982b186
> > fc450b157a94785c78b321b75abca9e90eb1a364230c65cf3852660b7e91f
> > httpcomponents-core-5.2.1-bin.zip httpcomponents-core-5.2.1-bin.zip
> >  
> > b60dd0726c111bf4c73237588de87abe9bacd7e3cde5f02b3f6a964ac8440bf95ec
> > 314bc31c493be2bb575ec12c6b998817c077e28c0688c67a7c56d85808406
> > httpcomponents-core-5.2.1-src.tar.gz httpcomponents-core-5.2.1-
> > src.tar.gz
> >  
> > f45027c559d970f4d25431a0b4660c6d7f26da887a1e76e42d3127eca4e3a831f6e
> > 9a3ff5684e1e4e223f525c0848843b0e9a09db16cb3c0ca4c86c341b8da87
> > httpcomponents-core-5.2.1-bin.tar.gz httpcomponents-core-5.2.1-
> > bin.tar.gz
> >  
> > 4e988abb987813c00da3f0624fe99c9ee1c38a84f3e0bad9c3a7b8a3d230400ff40
> > b24fb0083716d372243f0b5da4fadacb72224fbff2b0c6675c70a0ce110da
> > httpcomponents-core-5.2.1-src.zip httpcomponents-core-5.2.1-src.zip
> > 
> > Keys:
> >   https://www.apache.org/dist/httpcomponents/httpcore/KEYS
> 
> Re:
> 
> > * I/O reactor connect process redesign.
> >   Contributed by Oleg Kalnichevski <olegk at apache.org>
> 
> When I read redesign I comes to my mind that this shouldn't be in a 
> patch version, no? Looking at
> ebc1d6a560f9980ecff9ea3e4b1263eedd846528 I 
> can't really say what the impact is.

It was necessary in order to fix the SOCKS protocol handling. There are
no API visible changes, all changes are internal, so I do not
understand why this cannot be in a patch release.

Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org

Reply via email to