I am the release manager, but adding my vote here as well for the record.

+1 (binding)

src:
- verified hash and signature
- checked LICENSE, NOTICE, DISCLAIMER
- ran RAT check
- ran integration tests
- ran unit tests and compiled binary distribution
- ran native batch and kafka quickstart examples from the compiled binary

bin:
- verified hash and signature
- checked LICENSE, NOTICE, DISCLAIMER
- ran native batch and kafka quickstart examples


On Fri, Dec 6, 2019 at 12:45 AM Jihoon Son <jihoon...@apache.org> wrote:

> +1 (binding)
>
> src package:
> - verified signature and hash
> - checked LICENSE and NOTICE
> - built binary distribution and ran unit/integration tests
> - ran kafka/native batch quickstart
>
> bin package:
> - verified signature and hash
> - checked LICENSE and NOTICE
> - ran kafka/native batch quickstart
>
> Jihoon
>
> On Thu, Dec 5, 2019 at 2:39 PM Clint Wylie <cwy...@apache.org> wrote:
>
> > +1 (non-binding)
> >
> > src package:
> > - verified signature/hash
> > - ran RAT check
> > - checked for LICENSE, NOTICE, and DISCLAIMER
> > - compiled and ran unit tests
> > - built binary distribution, ran quickstart on built artifacts
> >
> > bin package:
> > - verified signature/hash
> > - checked for LICENSE, NOTICE, and DISCLAIMER
> > - ran quickstart
> >
> > On Wed, Dec 4, 2019 at 12:47 PM David Lim <david...@apache.org> wrote:
> >
> > > +1 (binding)
> > >
> > > src package:
> > > - verified signature/hash
> > > - compared source distribution contents against git tag (144bd78)
> > > - LICENSE, NOTICE, and DISCLAIMER are present
> > > - unit tests passed
> > > - licenses checked
> > > - built binary distribution
> > > - ran quickstart
> > >
> > > bin package:
> > > - verified signature/hash
> > > - verified META-INF/MANIFEST.MF:Build-Revision tag in JAR files matches
> > > source distribution git.version:Build-Revision (144bd78)
> > > - LICENSE, NOTICE, and DISCLAIMER are present
> > > - ran quickstart
> > >
> > > On Tue, Dec 3, 2019 at 6:20 PM Jonathan Wei <jon...@apache.org> wrote:
> > >
> > > > Hi all,
> > > >
> > > > I have created a build for Apache Druid (incubating) 0.16.1, release
> > > > candidate 2.
> > > >
> > > > Thanks for everyone who has helped contribute to the release! You can
> > > read
> > > > the proposed release notes here:
> > > > https://github.com/apache/incubator-druid/issues/8972
> > > >
> > > > The release candidate has been tagged in GitHub as
> > > > druid-0.16.1-incubating-rc2
> (144bd782964cac3d3d31f21b9e03b3c215f7f42d),
> > > > available here:
> > > >
> > > >
> > >
> >
> https://github.com/apache/incubator-druid/releases/tag/druid-0.16.1-incubating-rc2
> > > >
> > > > The artifacts to be voted on are located here:
> > > >
> > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/druid/0.16.1-incubating-rc2/
> > > >
> > > > Staged druid.apache.org website documentation is available here:
> > > >
> > https://druid.staged.apache.org/docs/0.16.1-incubating/design/index.html
> > > >
> > > > A Docker image containing the binary of the release candidate can be
> > > > retrieved via:
> > > > docker pull apache/incubator-druid:0.16.1-incubating-rc2
> > > >
> > > > artifact checksums
> > > > src:
> > > >
> > > >
> > >
> >
> 5644217e475885782bca18928cdfcbc75f3e95ace55ea11238f4350ea25b39a7febbca3e58d7de7d5145633a1e549f9022596ec65486b963c1978537c9a138dc
> > > > bin:
> > > >
> > > >
> > >
> >
> f637453dfbdec4b22384e9bf8ebe93ccf17898e8f0ebc45312ca71aa7e3722dc79f558e6792fd67619d3c3abc219487777e08e2fd8fe63d4c108a01330961fca
> > > > docker:
> > 169ca79ea8f8623c08cef32d0570260b96c5c68fbb839e308afa41a75e2cec60
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/jonwei.asc
> > > >
> > > > This key and the key of other committers can also be found in the
> > > project's
> > > > KEYS file here:
> > > > https://dist.apache.org/repos/dist/release/incubator/druid/KEYS
> > > >
> > > > (If you are a committer, please feel free to add your own key to that
> > > file
> > > > by following the instructions in the file's header.)
> > > >
> > > > Verify checksums:
> > > > diff <(shasum -a512 apache-druid-0.16.1-incubating-src.tar.gz | \
> > > > cut -d ' ' -f1) \
> > > > <(cat apache-druid-0.16.1-incubating-src.tar.gz.sha512 ; echo)
> > > >
> > > > diff <(shasum -a512 apache-druid-0.16.1-incubating-bin.tar.gz | \
> > > > cut -d ' ' -f1) \
> > > > <(cat apache-druid-0.16.1-incubating-bin.tar.gz.sha512 ; echo)
> > > >
> > > > Verify signatures:
> > > > gpg --verify apache-druid-0.16.1-incubating-src.tar.gz.asc \
> > > > apache-druid-0.16.1-incubating-src.tar.gz
> > > >
> > > > gpg --verify apache-druid-0.16.1-incubating-bin.tar.gz.asc \
> > > > apache-druid-0.16.1-incubating-bin.tar.gz
> > > >
> > > > Please review the proposed artifacts and vote. Note that Apache has
> > > > specific requirements that must be met before +1 binding votes can be
> > > cast
> > > > by PMC members. Please refer to the policy at
> > > > http://www.apache.org/legal/release-policy.html#policy for more
> > details.
> > > >
> > > > As part of the validation process, the release artifacts can be
> > generated
> > > > from source by running:
> > > > mvn clean install -Papache-release,dist -Dgpg.skip
> > > >
> > > > The RAT license check can be run from source by:
> > > > mvn apache-rat:check -Prat
> > > >
> > > > This vote will be open for at least 72 hours. The vote will pass if a
> > > > majority of at least three +1 PMC votes are cast.
> > > >
> > > > Once the vote has passed, the second stage vote will be called on the
> > > > Apache Incubator mailing list to get approval from the Incubator PMC.
> > > >
> > > > [ ] +1 Release this package as Apache Druid (incubating) 0.16.0
> > > > [ ] 0 I don't feel strongly about it, but I'm okay with the release
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > > >
> > > > Apache Druid (incubating) is an effort undergoing incubation at The
> > > Apache
> > > > Software Foundation (ASF), sponsored by the Apache Incubator.
> > Incubation
> > > is
> > > > required of all newly accepted projects until a further review
> > indicates
> > > > that the infrastructure, communications, and decision making process
> > have
> > > > stabilized in a manner consistent with other successful ASF projects.
> > > While
> > > > incubation status is not necessarily a reflection of the completeness
> > or
> > > > stability of the code, it does indicate that the project has yet to
> be
> > > > fully endorsed by the ASF.
> > > >
> > >
> >
>

Reply via email to