On Thu, Feb 04, 2016 at 09:50AM, Andrew Purtell wrote: > Let's try again next week. This is clearly not a good time for folks. I > think we could also hold the next vote open as long as it is necessary to > collect three votes from the PMC.
Well, in the last 3 releases I can recall the vote was done within the same reasonable timeframe. But sure. I won't be able to redo the vote though, as I am traveling with only a 3G inet access. If anyone want to run the release processes once again - please do. Cos > > On Feb 4, 2016, at 3:36 AM, Konstantin Boudnik <[email protected]> wrote: > > > > 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 > > > >
signature.asc
Description: Digital signature
