+1 from myself

On Wed, Jan 13, 2016 at 11:35 AM, Poorna Chandra <[email protected]> wrote:
> +1
>
> Build and tests pass
> Verified hashes
>
> Poorna.
>
> On Wed, Jan 13, 2016 at 10:26 AM, Henry Saputra <[email protected]>
> wrote:
>
>> Signature file looks good
>> Hash files look good
>> LICENSE file looks good
>> NOTICE file looks good
>> DISCLAIMER file exist
>> No third party executables
>> Source compiled and passed all tests
>>
>> +1 (binding)
>>
>> On Mon, Jan 11, 2016 at 10:42 AM, Terence Yim <[email protected]> wrote:
>>
>> > Hi all,
>> >
>> > This is a call for a vote on releasing Apache Twill 0.7.0-incubating,
>> > release candidate 1. This is the eighth release of Twill.
>> >
>> > The source tarball, including signatures, digests, etc. can be found at:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/twill/0.7.0-incubating-rc1/src
>> >
>> > The tag to be voted upon is v0.7.0-incubating:
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=shortlog;h=refs/tags/v0.7.0-incubating
>> >
>> > The release hash is 047e011f25066805eb820ff661364937ef7ef043:
>> >
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-twill.git;a=commit;h=047e011f25066805eb820ff661364937ef7ef043
>> >
>> > The Nexus Staging URL:
>> > https://repository.apache.org/content/repositories/orgapachetwill-1018
>> >
>> > Release artifacts are signed with the following key:
>> > https://people.apache.org/keys/committer/chtyim.asc
>> >
>> > KEYS file available:
>> > https://dist.apache.org/repos/dist/dev/incubator/twill/KEYS
>> >
>> > For information about the contents of this release, see:
>> >
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/twill/0.7.0-incubating-rc1/CHANGES.txt
>> >
>> > Please vote on releasing this package as Apache Twill 0.7.0-incubating
>> >
>> > The vote will be open for 72 hours.
>> >
>> > [ ] +1 Release this package as Apache Twill 0.7.0-incubating
>> > [ ] +0 no opinion
>> > [ ] -1 Do not release this package because ...
>> >
>> > Thanks,
>> > Terence Yim
>> >
>>

Reply via email to