Thanks for your help to verify the rc1, @colin and @Sravya. The following 
problems Sravya mentioned I will take over and fix it. But I have some puzzle 
about the problem item 2.
Hi @Sravya, you said it was recommend to delete the old tag and recreate a new 
one. Take this release for example, I currently send the voting email on the 
1.5.0-rc1. If none is oppose to this
1.5.0-rc1, this candidate will be final release. But according to your 
suggestion, I should delete the rc1 tag and recreate a tag 1.5.0. That's the 
question I want to ask for help. When I create a new tag 1.5.0,
Should I need to send the voting email on new tag 1.5.0. Thanks.

Regard
gqshen 

-----Original Message-----
From: Sravya Tirukkovalur [mailto:[email protected]] 
Sent: Wednesday, June 17, 2015 5:17 AM
To: dev
Subject: Re: [VOTE] Release Sentry incubating version 1.5.0 (rc1)

Verified following:

   - Format is in apache-$project-$version-incubating.tar.gz
   - Verified Signatures and hashes
   - git tag matches the released bits (diff -rf)
   - Can compile successfully from source
   - Verify DISCLAIMER, NOTICE and LICENCE (year etc)
   - All files have correct headers (Rat check should be clean - mvn verify)
   - No jar files or the like in the release


Some minor issues:

   1. It was recommended to host the RC bits @
   https://dist.apache.org/repos/dist/dev/incubator/sentry as mentioned in
   this thread
   
<http://mail-archives.apache.org/mod_mbox/incubator-general/201506.mbox/%3C87800125-0A58-43DA-A2DB-718B16232200%40me.com%3E>.
   Also it is mentioned in our how to release wiki:
   
https://cwiki.apache.org/confluence/display/SENTRY/How+to+Release#HowtoRelease-Uploadartifacts
   2. It was actually recommended in one of our previous release to delete
   the old tag and recreate the new tag, our wiki also reflects this.
   3. Changelog is not upto date, looks like there are atleast a couple
   jiras missing:
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314720&version=12327461


-1, due to above issues. @Guoquan: Will it be possible to fix the above
issues? Although I think some of the above are not release blockers, I
think it would be better to fix them.

Thanks!

On Tue, Jun 16, 2015 at 1:05 AM, Ma, Junjie <[email protected]> wrote:

> +1
>
> I checked the checksums, LICENSE, NOTICE, DISCLAIMER, get the tarball,
> compiled and ran the tests.
>
> Best regards,
>
> Colin Ma(Ma Jun Jie)
>
> -----Original Message-----
> From: gqshen [mailto:[email protected]]
> Sent: Tuesday, June 16, 2015 9:49 AM
> To: [email protected]
> Subject: [VOTE] Release Sentry incubating version 1.5.0 (rc1)
>
> This is the incubator release of Apache Sentry, version 1.5.0-incubating.
>
> The list of fixed issues, added features and improvements can be found
> here:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=blob;f=CHANGELOG.txt;h=5d96434653aa292dfd025c7baa876013e95a5a15;hb=refs/heads/branch-1.5.0
>
> Source files : http://people.apache.org/~gqshen/sentry-1.5.0-rc1/
>
> Tag to be voted on (release 1.5.0-rc1/SHA:
> 3bf4ece59d8c4bc05ba96e4c9fab8b768e95b090):
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-sentry.git;a=commit;h=3bf4ece59d8c4bc05ba96e4c9fab8b768e95b090
> Sentry's KEYS containing the PGP key we used to sign the release:
> http://www.apache.org/dist/incubator/sentry/KEYS
>
> Note that this is a source only release and we are voting on the source:
> tag=release-1.5.0-rc1, SHA=3bf4ece59d8c4bc05ba96e4c9fab8b768e95b090
>
> Vote will be opened for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thank you for your prompt votes.
>
> Thanks to Prasad and Sravya for all your help and guidance...
>
> Respectfully,
> Sentry 1.5.0 Release Manager (Guoquan Shen)
>



-- 
Sravya Tirukkovalur

Reply via email to