Please vote on releasing these packages as HttpComponents Core 4.2.5.
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:
Please vote on releasing these packages as HttpComponents Core 4.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:
On 16 July 2013 20:43, Oleg Kalnichevski ol...@apache.org wrote:
Please vote on releasing these packages as HttpComponents Core 4.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
On 16 July 2013 20:43, Oleg Kalnichevski ol...@apache.org wrote:
Please vote on releasing these packages as HttpComponents Core 4.2.5.
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
We need to include the revision number as well as the SVN tag.
We don't re-use tags (I hope!), but SVN does not guarantee tag
immutability, so for completeness the revision is needed.
It's easy enough to copy/paste from the commit mail.
The KEYS file is needed so an outsider can easily check the
Do we really need separate KEYS files for httpcore/client etc?
Could we not just have a complete set at the top-level?
It will mean updating a few links, but I'm happy to do that if there
is agreement to merge them.
Maybe start by creating merged KEYS file, and gradually update links;
Should the keys file be in the email? Or a rev no of the keys file?
Gary
On Jul 16, 2013, at 18:29, sebb seb...@gmail.com wrote:
We need to include the revision number as well as the SVN tag.
We don't re-use tags (I hope!), but SVN does not guarantee tag
immutability, so for completeness the
