The following source files don't have AL headers:

settings.gradle
src/main/AndroidManifest.xml


The first one is a single line so does not need a header, but the
second is bigger and should probably be given a header.
Not a blocker but should be fixed for the future.

The NOTICE and LICENSE files in the jars are at the top-level.
Normally these are under META-INF - not a blocker.

The source in the source jar agrees with the SVN tag, but only
includes the Java source.
There does not appear to be a source archive which is necessary for
all ASF releases.

Checked
So I have to vote -1 unless I have overlooked the ASF source archive somewhere.

Also it is helpful to include the KEYS file link in a vote e-mail.


On 10 March 2014 09:18, Oleg Kalnichevski <[email protected]> wrote:
> Please vote on releasing these packages as HttpComponents Client Android
> port 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.
>
> Readme:
> http://svn.apache.org/repos/asf/httpcomponents/httpclient-android/tags/4.3.3-RC1/README.txt
>
> Maven artefacts:
> https://repository.apache.org/content/repositories/orgapachehttpcomponents-1008/org/apache/httpcomponents/httpclient-android/4.3.3/
>
> SVN tag:
> http://svn.apache.org/repos/asf/httpcomponents/httpclient-android/tags/4.3.3-RC1/
> revision 1575871
>
> --------------------------------------------------------------------------
> Vote: HttpComponents Client Android port 4.3.3 release
> [ ] +1 Release the packages as HttpComponents Client Android port 4.3.3.
> [ ] -1 I am against releasing the packages (must include a reason).
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to