On 22 February 2014 14:48, Gary Gregory <[email protected]> wrote: > Please vote on releasing these packages as HttpComponents Client 4.3.3. > 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. > > Packages: > https://dist.apache.org/repos/dist/dev/httpcomponents/httpclient-4.3.3-RC1 > revision 4476
The KEY is missing from the KEYS file on the dist site. I think this is a release blocker. However the key has been published, and the sigs work against the KEYS file in SVN. Hashes OK where provided. Also just noticed that there are no SHA1 hashes for the release packages This is not a release blocker, but we should perhaps consider for future releases. tar.gz and zip archives agree with each other (allowing for EOL diffs) > Release notes: > https://dist.apache.org/repos/dist/dev/httpcomponents/httpclient-4.3.3-RC1/RELEASE_NOTES-4.3.x.txt > > Maven artefacts: > https://repository.apache.org/content/repositories/orgapachehttpcomponents-1007 > > SVN tag: > https://svn.apache.org/repos/asf/httpcomponents/httpclient/tags/4.3.3-RC1 > revision 1570731 RAT and SVN properties look OK Source archive agrees with tag except for files like doap that don't gert published. > -------------------------------------------------------------------------- > Vote: HttpComponents Client 4.3.3 release > [ ] +1 Release the packages as HttpComponents Client 4.3.3. > [ ] -1 I am against releasing the packages (must include a reason). -1 at present; the KEYS issue needs to be sorted before release can proceed. > Gary > -- > E-Mail: [email protected] | [email protected] > Java Persistence with Hibernate, Second > Edition<http://www.manning.com/bauer3/> > JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> > Spring Batch in Action <http://www.manning.com/templier/> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
