I've built the 1.1 slave images based on sombody's configured jenkins job and pushed them to dockerhub. Although we haven't release 1.1 yet but images can unlock the tests. Its much more confident to me if I at lease see features at a all green status on CI for the 1.1 branch. Can we renegotiate the deadline? To me I can give feedback no late than 2/6. Thanks for puting on the vote, cos. 2016年2月4日 下午7:39 於 "Konstantin Boudnik" <[email protected]> 寫道：
> The release [VOTE] has failed as not a single vote has been casted. > > On Sat, Jan 30, 2016 at 08:35PM, Konstantin Boudnik wrote: > > This is the vote for release 1.1.0 of Apache Bigtop. > > > > It fixes the following issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311420&version=12329714 > > > > The vote will be going for at least 72 hours and will be closed on > Wednesday, > > February 3rd, 2016 at noon PDT. Please download, test and vote with > > > > [ ] +1, accept rc1 as the official 1.1.0 release of Apache Bigtop > > [ ] +0, I don't care either way, > > [ ] -1, do not accept rc1 as the official 1.1.0 release of Apache > Bigtop, because... > > > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/bigtop/1.1.0-rc1 > > > > Maven staging repo: > > > https://repository.apache.org/content/repositories/orgapachebigtop-1006 > > > > The git tag to be voted upon is release-1.1.0 > > > > Bigtop's KEYS file containing PGP keys we use to sign the release: > > https://dist.apache.org/repos/dist/release/bigtop/KEYS > > > > Thanks! > > Cos > > >
