Hi Roman, Thanks for you efforts! CI looks really good now.
What was the consensus for the BIGTOP-2716 <https://issues.apache.org/jira/browse/BIGTOP-2716> ? We only support the current bigtop/slaves docker images, knowing it will break if regenerated? Fine for me. Greetings, Olaf > Am 30.03.2017 um 03:51 schrieb Roman Shaposhnik <[email protected]>: > > This is the vote for release 1.2.0 of Apache Bigtop. > > It fixes the following issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311420&version=12334717 > > The vote will close on Tuesday, April 4th, 2017 at noon PDT. > Please download, test and vote with > > [ ] +1, accept RC1 as the official 1.2.0 release of Apache Bigtop > [ ] +0, I don't care either way, > [ ] -1, do not accept RC1 as the official 1.2.0 release of Apache > Bigtop, because... > > Source and binary files: > https://dist.apache.org/repos/dist/dev/bigtop/1.2.0-RC1 > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachebigtop-1010 > > The git tag to be voted upon is rel/1.2.0-RC1 > > The convenience binary artifacts are available for testing at the locations > indicated by repo file. The easiest way to test those is to use our docker > provisioner. E.g. > $ cd provisioner/docker > $ ./docker-hadoop.sh -C config_XXX.yaml -c 3 > > Bigtop's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/bigtop/KEYS > > Thanks, > Roman.
signature.asc
Description: Message signed with OpenPGP
