You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aurora.apache.org by John Sirois <js...@apache.org> on 2016/02/05 20:57:31 UTC

[RESULT][VOTE] Release Apache Aurora 0.12.0 RC3

Due to a new backfill issue found by Maxim [1], I'm cancelling this vote.
I'll start a new release when that issue is resolved and we've all had time
to re-assess RC status.

[1] https://issues.apache.org/jira/browse/AURORA-1610

On Fri, Feb 5, 2016 at 12:10 PM, John Sirois <js...@apache.org> wrote:

> All,
>
> I propose that we accept the following release candidate as the official
> Apache Aurora 0.12.0 release.
>
> Aurora 0.12.0-rc3 includes the following:
> ---
> The NEWS for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=aurora.git&f=NEWS&hb=rel/0.12.0-rc3
>
> The CHANGELOG for the release is available at:
>
> https://git-wip-us.apache.org/repos/asf?p=aurora.git&f=CHANGELOG&hb=rel/0.12.0-rc3
>
> The tag used to create the release candidate is:
>
> https://git-wip-us.apache.org/repos/asf?p=aurora.git;a=shortlog;h=refs/tags/rel/0.12.0-rc3
>
> The release candidate is available at:
>
> https://dist.apache.org/repos/dist/dev/aurora/0.12.0-rc3/apache-aurora-0.12.0-rc3.tar.gz
>
> The MD5 checksum of the release candidate can be found at:
>
> https://dist.apache.org/repos/dist/dev/aurora/0.12.0-rc3/apache-aurora-0.12.0-rc3.tar.gz.md5
>
> The signature of the release candidate can be found at:
>
> https://dist.apache.org/repos/dist/dev/aurora/0.12.0-rc3/apache-aurora-0.12.0-rc3.tar.gz.asc
>
> The GPG key used to sign the release are available at:
> https://dist.apache.org/repos/dist/dev/aurora/KEYS
>
> Please download, verify, and test.
>
> The vote will close on Mon Feb  8 12:06:46 MST 2016
>
> [ ] +1 Release this as Apache Aurora 0.12.0
> [ ] +0
> [ ] -1 Do not release this as Apache Aurora 0.12.0 because...
> ---
>
> Reminder: you can verify the release candidate via:
>
>   ./build-support/release/verify-release-candidate 0.12.0-rc3
>
> If you can deploy the RC to a test cluster and evaluate it there, even
> better.
>