Previous message sent from wrong email, please ignore. +1 (binding)
src: - verified hash and signature - checked LICENSE, NOTICE, DISCLAIMER - ran unit tests and compiled binary distribution - ran RAT check - ran integration tests - ran all of the quickstart ingestion tutorials from the compiled binary bin: - verified hash and signature - checked LICENSE, NOTICE, DISCLAIMER - ran all of the quickstart ingestion tutorials - verified META-INF/MANIFEST.MF:Build-Revision tag in JAR files matches source distribution git.version (1053684f388ea68e8e9fc618579867201a8e032b) On Mon, May 13, 2019 at 6:23 PM Jonathan Wei <w32...@gmail.com> wrote: > +1 (binding) > > src: > - verified hash and signature > - checked LICENSE, NOTICE, DISCLAIMER > - ran unit tests and compiled binary distribution > - ran RAT check > - ran integration tests > - ran all of the quickstart ingestion tutorials from the compiled binary > > bin: > - verified hash and signature > - checked LICENSE, NOTICE, DISCLAIMER > - ran all of the quickstart ingestion tutorials > - verified META-INF/MANIFEST.MF:Build-Revision tag in JAR files matches > source distribution git.version (1053684f388ea68e8e9fc618579867201a8e032b) > > > On Mon, May 13, 2019 at 4:29 PM Jihoon Son <jihoon...@apache.org> wrote: > >> +1 >> >> src package: >> - verified signature/hash >> - LICENSE, NOTICE, and DISCLAIMER are present >> - unit tests passed >> - RAT check passed >> - built binary distribution >> - ran quickstart tutorials: kafka indexing service and batch index task >> >> bin package: >> - verified signature/hash >> - LICENSE, NOTICE, and DISCLAIMER are present >> - ran quickstart tutorials: kafka indexing service and batch index task >> >> Jihoon >> >> On Mon, May 13, 2019 at 7:26 AM Slim Bouguerra <bs...@apache.org> wrote: >> >> > 0 for me >> > We have just released 0.14.0 and 0.14.1 and soon will be releasing >> 0.15.0, >> > This release is effectively one bug fix that concerns one extension. >> > IMO this is a read flag of unstable release that can hurt the project >> > overall, we need to keep in mind that Druid is not a library but it is a >> > Distributed Database, and upgrades are by nature lengthy/costly process. >> > >> > On Fri, May 10, 2019 at 3:10 PM Clint Wylie <cwy...@apache.org> wrote: >> > >> > > Hi all, >> > > >> > > I have created a build for Apache Druid (incubating) 0.14.2, release >> > > candidate 1. >> > > >> > > This is a bug fix release that contains a small number of important >> fixes >> > > for 0.14.x. You can read the proposed release notes here: >> > > https://github.com/apache/incubator-druid/issues/7628 >> > > >> > > The release candidate has been tagged in GitHub as >> > > druid-0.14.2-incubating-rc1 (1053684), available here: >> > > >> > > >> > >> https://github.com/apache/incubator-druid/releases/tag/druid-0.14.2-incubating-rc1 >> > > >> > > The artifacts to be voted on are located here: >> > > >> > > >> > >> https://dist.apache.org/repos/dist/dev/incubator/druid/0.14.2-incubating-rc1/ >> > > >> > > Release artifacts are signed with the following key: >> > > https://people.apache.org/keys/committer/cwylie.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.) >> > > >> > > 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 >> > > >> > > 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.14.2 >> > > [ ] 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. >> > > >> > >> >
