[VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[David Lim]

Hi all,

I have created a build for Apache Druid (incubating) 0.13.0, release
candidate 1.

Thanks to everyone who has contributed to this release! You can read the
proposed release notes here:
https://github.com/apache/incubator-druid/issues/6442

The release candidate has been tagged in GitHub as
druid-0.13.0-incubating-rc1 (acf15b4), available here:
https://github.com/apache/incubator-druid/releases/tag/druid-0.13.0-incubating-rc1

The artifacts to be voted on are located here:
https://dist.apache.org/repos/dist/dev/incubator/druid/apache-druid-0.13.0-incubating-rc1/

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/davidlim.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/dev/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. As this is our first release
under the Apache Incubator program, 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 -Dtar

This vote will be open for at least 72 hours but likely more, in following
the Druid community's practice of deploying the RC to larger clusters and
allowing it to soak for a period of time to flush out any remaining issues.
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.13.0
[ ]  0 I don't feel strongly about it, but I'm okay with the release
[ ] -1 Do not release this package because...

Thanks!
David

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Slim Bouguerra]

+1

> On Oct 21, 2018, at 8:41 AM, David Lim  wrote:
> 
> Hi all,
> 
> I have created a build for Apache Druid (incubating) 0.13.0, release
> candidate 1.
> 
> Thanks to everyone who has contributed to this release! You can read the
> proposed release notes here:
> https://github.com/apache/incubator-druid/issues/6442
> 
> The release candidate has been tagged in GitHub as
> druid-0.13.0-incubating-rc1 (acf15b4), available here:
> https://github.com/apache/incubator-druid/releases/tag/druid-0.13.0-incubating-rc1
> 
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/druid/apache-druid-0.13.0-incubating-rc1/
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/davidlim.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/dev/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. As this is our first release
> under the Apache Incubator program, 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 -Dtar
> 
> This vote will be open for at least 72 hours but likely more, in following
> the Druid community's practice of deploying the RC to larger clusters and
> allowing it to soak for a period of time to flush out any remaining issues.
> 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.13.0
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
> 
> Thanks!
> David


-
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
For additional commands, e-mail: dev-h...@druid.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Julian Hyde]

Hey Slim,

Since this is an Apache release, and you've voted on Apache releases
before in Calcite and Hive, can you explain what you checked before
you voted "+1". There are many folks here who have not been through
the release process, and we veterans should show them the ropes.

Julian

On Sun, Oct 21, 2018 at 1:16 PM Slim Bouguerra  wrote:
>
> +1
>
> > On Oct 21, 2018, at 8:41 AM, David Lim  wrote:
> >
> > Hi all,
> >
> > I have created a build for Apache Druid (incubating) 0.13.0, release
> > candidate 1.
> >
> > Thanks to everyone who has contributed to this release! You can read the
> > proposed release notes here:
> > https://github.com/apache/incubator-druid/issues/6442
> >
> > The release candidate has been tagged in GitHub as
> > druid-0.13.0-incubating-rc1 (acf15b4), available here:
> > https://github.com/apache/incubator-druid/releases/tag/druid-0.13.0-incubating-rc1
> >
> > The artifacts to be voted on are located here:
> > https://dist.apache.org/repos/dist/dev/incubator/druid/apache-druid-0.13.0-incubating-rc1/
> >
> > Release artifacts are signed with the following key:
> > https://people.apache.org/keys/committer/davidlim.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/dev/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. As this is our first release
> > under the Apache Incubator program, 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 -Dtar
> >
> > This vote will be open for at least 72 hours but likely more, in following
> > the Druid community's practice of deploying the RC to larger clusters and
> > allowing it to soak for a period of time to flush out any remaining issues.
> > 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.13.0
> > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > [ ] -1 Do not release this package because...
> >
> > Thanks!
> > David
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> For additional commands, e-mail: dev-h...@druid.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
For additional commands, e-mail: dev-h...@druid.apache.org

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Fangjin Yang]

+1

On Sun, Oct 21, 2018 at 3:34 PM Julian Hyde  wrote:

> Hey Slim,
>
> Since this is an Apache release, and you've voted on Apache releases
> before in Calcite and Hive, can you explain what you checked before
> you voted "+1". There are many folks here who have not been through
> the release process, and we veterans should show them the ropes.
>
> Julian
>
> On Sun, Oct 21, 2018 at 1:16 PM Slim Bouguerra 
> wrote:
> >
> > +1
> >
> > > On Oct 21, 2018, at 8:41 AM, David Lim  wrote:
> > >
> > > Hi all,
> > >
> > > I have created a build for Apache Druid (incubating) 0.13.0, release
> > > candidate 1.
> > >
> > > Thanks to everyone who has contributed to this release! You can read
> the
> > > proposed release notes here:
> > > https://github.com/apache/incubator-druid/issues/6442
> > >
> > > The release candidate has been tagged in GitHub as
> > > druid-0.13.0-incubating-rc1 (acf15b4), available here:
> > >
> https://github.com/apache/incubator-druid/releases/tag/druid-0.13.0-incubating-rc1
> > >
> > > The artifacts to be voted on are located here:
> > >
> https://dist.apache.org/repos/dist/dev/incubator/druid/apache-druid-0.13.0-incubating-rc1/
> > >
> > > Release artifacts are signed with the following key:
> > > https://people.apache.org/keys/committer/davidlim.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/dev/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. As this is our first
> release
> > > under the Apache Incubator program, 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 -Dtar
> > >
> > > This vote will be open for at least 72 hours but likely more, in
> following
> > > the Druid community's practice of deploying the RC to larger clusters
> and
> > > allowing it to soak for a period of time to flush out any remaining
> issues.
> > > 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.13.0
> > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > [ ] -1 Do not release this package because...
> > >
> > > Thanks!
> > > David
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> > For additional commands, e-mail: dev-h...@druid.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> For additional commands, e-mail: dev-h...@druid.apache.org
>
>

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Slim Bouguerra]

Hey Julian
Thanks for pointing that out.

For the Apache related major changes please carefully review
https://github.com/apache/incubator-druid/labels/Apache
For bugs/features the release note is what you want to check
https://github.com/apache/incubator-druid/issues/6442/


On Sun, Oct 21, 2018 at 6:38 PM Fangjin Yang  wrote:

> +1
>
> On Sun, Oct 21, 2018 at 3:34 PM Julian Hyde  wrote:
>
> > Hey Slim,
> >
> > Since this is an Apache release, and you've voted on Apache releases
> > before in Calcite and Hive, can you explain what you checked before
> > you voted "+1". There are many folks here who have not been through
> > the release process, and we veterans should show them the ropes.
> >
> > Julian
> >
> > On Sun, Oct 21, 2018 at 1:16 PM Slim Bouguerra  >
> > wrote:
> > >
> > > +1
> > >
> > > > On Oct 21, 2018, at 8:41 AM, David Lim  wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I have created a build for Apache Druid (incubating) 0.13.0, release
> > > > candidate 1.
> > > >
> > > > Thanks to everyone who has contributed to this release! You can read
> > the
> > > > proposed release notes here:
> > > > https://github.com/apache/incubator-druid/issues/6442
> > > >
> > > > The release candidate has been tagged in GitHub as
> > > > druid-0.13.0-incubating-rc1 (acf15b4), available here:
> > > >
> >
> https://github.com/apache/incubator-druid/releases/tag/druid-0.13.0-incubating-rc1
> > > >
> > > > The artifacts to be voted on are located here:
> > > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/druid/apache-druid-0.13.0-incubating-rc1/
> > > >
> > > > Release artifacts are signed with the following key:
> > > > https://people.apache.org/keys/committer/davidlim.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/dev/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. As this is our first
> > release
> > > > under the Apache Incubator program, 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 -Dtar
> > > >
> > > > This vote will be open for at least 72 hours but likely more, in
> > following
> > > > the Druid community's practice of deploying the RC to larger clusters
> > and
> > > > allowing it to soak for a period of time to flush out any remaining
> > issues.
> > > > 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.13.0
> > > > [ ]  0 I don't feel strongly about it, but I'm okay with the release
> > > > [ ] -1 Do not release this package because...
> > > >
> > > > Thanks!
> > > > David
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> > > For additional commands, e-mail: dev-h...@druid.apache.org
> > >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org
> > For additional commands, e-mail: dev-h...@druid.apache.org
> >
> >
>


-- 

B-Slim
___/\/\/\___/\/\/\___/\/\/\___/\/\/\___/\/\/\___

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[David Lim]

I believe what Julian wanted to highlight was this line in the announcement:

> As this is our first release under the Apache Incubator program, 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.

Some of the statements in that document:

- Before casting +1 binding votes, individuals are REQUIRED to:
- download all signed source code packages onto their own hardware
- verify that they meet all requirements of ASF policy on releases, for
example:
- Every ASF release MUST contain one or more source packages, which
MUST be sufficient for a user to build and test the release provided they
have access to the appropriate platform and tools
- All supplied packages MUST be cryptographically signed by the
Release Manager with a detached signature
- Binary/bytecode package MUST have the same version number as the
source release and MUST only add binary/bytecode files that are the result
of compiling that version of the source code release and its dependencies
- Each package MUST provide a LICENSE file and a NOTICE file which
account for the package's exact content. LICENSE and NOTICE MUST NOT
provide unnecessary information about materials which are not bundled in
the package, such as separately downloaded dependencies. For source
packages, LICENSE and NOTICE MUST be located at the root of the
distribution. For additional packages, they MUST be located in the
distribution format's customary location for licensing materials, such as
the META-INF directory of Java "jar" files.
- validate all cryptographic signatures
- compile as provided
- test the result on their own platform

Additionally, as an incubator project, we are required to have a DISCLAIMER
file indicating that we are undergoing incubation.

One question I have: for the binary tarball package, we have a LICENSE and
NOTICE file in the root of the distribution which is what we have always
done, but I have not also included these files in the individual JAR files
under META-INF. I thought that having them in the root would be sufficient,
but now I'm thinking they might actually also need to be in each JAR file
since those files will be made available through Maven independent of our
tarball packaging. I checked the Maven artifacts for previous versions of
Druid and they don't include the LICENSE and NOTICE file in the JAR, but it
feels to me like this will be required. Thoughts welcome.

David



On Mon, Oct 22, 2018 at 9:04 AM Slim Bouguerra 
wrote:

> Hey Julian
> Thanks for pointing that out.
>
> For the Apache related major changes please carefully review
> https://github.com/apache/incubator-druid/labels/Apache
> For bugs/features the release note is what you want to check
> https://github.com/apache/incubator-druid/issues/6442/
>
>
> On Sun, Oct 21, 2018 at 6:38 PM Fangjin Yang  wrote:
>
> > +1
> >
> > On Sun, Oct 21, 2018 at 3:34 PM Julian Hyde  wrote:
> >
> > > Hey Slim,
> > >
> > > Since this is an Apache release, and you've voted on Apache releases
> > > before in Calcite and Hive, can you explain what you checked before
> > > you voted "+1". There are many folks here who have not been through
> > > the release process, and we veterans should show them the ropes.
> > >
> > > Julian
> > >
> > > On Sun, Oct 21, 2018 at 1:16 PM Slim Bouguerra <
> slim.bougue...@gmail.com
> > >
> > > wrote:
> > > >
> > > > +1
> > > >
> > > > > On Oct 21, 2018, at 8:41 AM, David Lim 
> wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I have created a build for Apache Druid (incubating) 0.13.0,
> release
> > > > > candidate 1.
> > > > >
> > > > > Thanks to everyone who has contributed to this release! You can
> read
> > > the
> > > > > proposed release notes here:
> > > > > https://github.com/apache/incubator-druid/issues/6442
> > > > >
> > > > > The release candidate has been tagged in GitHub as
> > > > > druid-0.13.0-incubating-rc1 (acf15b4), available here:
> > > > >
> > >
> >
> https://github.com/apache/incubator-druid/releases/tag/druid-0.13.0-incubating-rc1
> > > > >
> > > > > The artifacts to be voted on are located here:
> > > > >
> > >
> >
> https://dist.apache.org/repos/dist/dev/incubator/druid/apache-druid-0.13.0-incubating-rc1/
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > > https://people.apache.org/keys/committer/davidlim.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/dev/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. As this is our first
> > > release
> > > > > under the Apach

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Julian Hyde]

Thanks for finding that list, David. There are a lot of things to check. 
Therefore, before voting +1 you need to do some due diligence, and with your 
vote you should describe how you validated the release.

For example, in a recent Calcite release thread[1] a typical vote looked like 
this:

> +1 (non-binding)
>  - downloaded, checked gpg and sha256
>  - compiled and ran tests ("mvn clean install") using JDK 8_162, 10.0.1 on 
> Fedora and Windows
>  - ran simple queries via sqlline

Everyone should download the artifacts, check sha256 and gpg (asc) signatures, 
and compile the code.

Julian

[1] 
https://lists.apache.org/thread.html/c85d5f3cf1bbd9e28d76acd6905dee83cb54334c8b5d8979e1894648@%3Cdev.calcite.apache.org%3E

> On Oct 22, 2018, at 10:47 AM, David Lim  wrote:
> 
> I believe what Julian wanted to highlight was this line in the announcement:
> 
>> As this is our first release under the Apache Incubator program, 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.
> 
> Some of the statements in that document:
> 
> - Before casting +1 binding votes, individuals are REQUIRED to:
>- download all signed source code packages onto their own hardware
>- verify that they meet all requirements of ASF policy on releases, for
> example:
>- Every ASF release MUST contain one or more source packages, which
> MUST be sufficient for a user to build and test the release provided they
> have access to the appropriate platform and tools
>- All supplied packages MUST be cryptographically signed by the
> Release Manager with a detached signature
>- Binary/bytecode package MUST have the same version number as the
> source release and MUST only add binary/bytecode files that are the result
> of compiling that version of the source code release and its dependencies
>- Each package MUST provide a LICENSE file and a NOTICE file which
> account for the package's exact content. LICENSE and NOTICE MUST NOT
> provide unnecessary information about materials which are not bundled in
> the package, such as separately downloaded dependencies. For source
> packages, LICENSE and NOTICE MUST be located at the root of the
> distribution. For additional packages, they MUST be located in the
> distribution format's customary location for licensing materials, such as
> the META-INF directory of Java "jar" files.
>- validate all cryptographic signatures
>- compile as provided
>- test the result on their own platform
> 
> Additionally, as an incubator project, we are required to have a DISCLAIMER
> file indicating that we are undergoing incubation.
> 
> One question I have: for the binary tarball package, we have a LICENSE and
> NOTICE file in the root of the distribution which is what we have always
> done, but I have not also included these files in the individual JAR files
> under META-INF. I thought that having them in the root would be sufficient,
> but now I'm thinking they might actually also need to be in each JAR file
> since those files will be made available through Maven independent of our
> tarball packaging. I checked the Maven artifacts for previous versions of
> Druid and they don't include the LICENSE and NOTICE file in the JAR, but it
> feels to me like this will be required. Thoughts welcome.
> 
> David
> 
> 
> 
> On Mon, Oct 22, 2018 at 9:04 AM Slim Bouguerra 
> wrote:
> 
>> Hey Julian
>> Thanks for pointing that out.
>> 
>> For the Apache related major changes please carefully review
>> https://github.com/apache/incubator-druid/labels/Apache
>> For bugs/features the release note is what you want to check
>> https://github.com/apache/incubator-druid/issues/6442/
>> 
>> 
>> On Sun, Oct 21, 2018 at 6:38 PM Fangjin Yang  wrote:
>> 
>>> +1
>>> 
>>> On Sun, Oct 21, 2018 at 3:34 PM Julian Hyde  wrote:
>>> 
 Hey Slim,
 
 Since this is an Apache release, and you've voted on Apache releases
 before in Calcite and Hive, can you explain what you checked before
 you voted "+1". There are many folks here who have not been through
 the release process, and we veterans should show them the ropes.
 
 Julian
 
 On Sun, Oct 21, 2018 at 1:16 PM Slim Bouguerra <
>> slim.bougue...@gmail.com
 
 wrote:
> 
> +1
> 
>> On Oct 21, 2018, at 8:41 AM, David Lim 
>> wrote:
>> 
>> Hi all,
>> 
>> I have created a build for Apache Druid (incubating) 0.13.0,
>> release
>> candidate 1.
>> 
>> Thanks to everyone who has contributed to this release! You can
>> read
 the
>> proposed release notes here:
>> https://github.com/apache/incubator-druid/issues/6442
>> 
>> The release candidate has been tagged in GitHub as
>> druid-0.13.0-incubating-rc1 (acf15b4), available here:
>> 
 
>>> 
>> https://github.com/apache/incubator-

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Julian Hyde]

-1 due to GPG error; but also see other concerns below and fix them if there 
are genuine issues.

As this is Druid’s first Apache release candidate, I am impressed by how many 
things you got right.

I have completely ignored bin.tar.gz. It’s not possible to “release” binaries 
in Apache because it’s not possible to audit binaries.

I downloaded and checked signatures. .sha512 is ok. GPG failed with “No public 
key” error:

$ gpg --verify apache-druid-0.13.0-incubating-src.tar.gz.asc 
apache-druid-0.13.0-incubating-src.tar.gz
gpg: Signature made Sat Oct 20 20:50:20 2018 PDT
gpg:using RSA key 58B5D669D2FFD83B37D88DF8BB64B3727183DE56
gpg: Can't check signature: No public key

src.tar.gz file contains files such as 
./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s.
 Is this expected/good/bad?

There are a few binary files in the release, e.g. index.zip, 
druid.sample.tsv.zip, wikiticker-2015-09-12-sampled.json.gz, 
indexing_service.png. Sometimes binary files are a concern, but I was able to 
inspect all of these in their respective editors.

I checked the contents of src.tar.gz against git commit acf15b4. There are a 
few differences, as follows. Are any of them surprising?

$ diff -r . /tmp/apache-druid-0.13.0-incubating-src/
Only in .: .git
Only in .: .gitignore
Only in .: .idea
Only in .: .travis.yml
Only in .: eclipse.importorder
Only in .: eclipse_formatting.xml
Only in 
/tmp/apache-druid-0.13.0-incubating-src/extensions-core/protobuf-extensions: 
dependency-reduced-pom.xml
Only in /tmp/apache-druid-0.13.0-incubating-src/: git.version
Only in ./integration-tests: .gitignore
Only in .: publications
Only in .: upload.sh

I could not find a list of instructions for how to build the source code. I 
checked README.md, CONTRIBUTING.md; there were some back-handed instructions in 
INTELLIJ_SETUP.md. In my opinion a source release should have instructions how 
to build, including a list of supported platforms (java versions, operating 
systems if applicable). As indeed should the home page.

Built the code successfully using “mvn -DskipTests install” and Java 8 on 
macOS. There were quite a few “[WARNING]” lines.

Glad to see that all .java files have headers. But quite a lot of files[1] do 
not. I saw that you added them as exclusions to apache-rat. Can you explain the 
thinking behind these exclusions?

Julian

[1] Files without headers

$ for i in $(git ls-files | egrep -v 
'test/resources|LICENSE|NOTICE|\.(png|pdf|zip|jpg)$'); do grep -s "Licensed to 
the Apache Software" $i >/dev/null || echo "$i"; done
.gitignore
.idea/inspectionProfiles/Druid.xml
.idea/inspectionProfiles/profiles_settings.xml
.idea/misc.xml
.idea/scopes/NonGeneratedFiles.xml
.idea/scopes/UnusedInspectionsScope.xml
.travis.yml
CONTRIBUTING.md
DISCLAIMER
INTELLIJ_SETUP.md
README.md
ci/README_TeamCity.md
codestyle/druid-forbidden-apis.txt
codestyle/joda-time-forbidden-apis.txt
common/src/main/antlr4/org/apache/druid/math/expr/antlr/Expr.g4
common/src/main/resources/services/javax.annotation.processing.Processor
docs/_bin/deploy-docs.sh
docs/_bin/get-milestone-contributors.py
docs/_bin/make-redirects.py
docs/_config.yml
docs/_graphics/druid-dataflow-3.svg
docs/_graphics/druid-dataflow.svg
docs/_graphics/druid-manage-1.svg
docs/_graphics/druid-production.svg
docs/_graphics/druid.graffle
docs/_graphics/indexing_service.dot
docs/_redirects.json
docs/content/comparisons/druid-vs-elasticsearch.md
docs/content/comparisons/druid-vs-key-value.md
docs/content/comparisons/druid-vs-kudu.md
docs/content/comparisons/druid-vs-redshift.md
docs/content/comparisons/druid-vs-spark.md
docs/content/comparisons/druid-vs-sql-on-hadoop.md
docs/content/configuration/index.md
docs/content/configuration/logging.md
docs/content/configuration/realtime.md
docs/content/dependencies/cassandra-deep-storage.md
docs/content/dependencies/deep-storage.md
docs/content/dependencies/metadata-storage.md
docs/content/dependencies/zookeeper.md
docs/content/design/auth.md
docs/content/design/broker.md
docs/content/design/coordinator.md
docs/content/design/historical.md
docs/content/design/index.md
docs/content/design/indexing-service.md
docs/content/design/middlemanager.md
docs/content/design/overlord.md
docs/content/design/peons.md
docs/content/design/plumber.md
docs/content/design/realtime.md
docs/content/design/segments.md
docs/content/development/build.md
docs/content/development/experimental.md
docs/content/development/extensions-contrib/ambari-metrics-emitter.md
docs/content/development/extensions-contrib/azure.md
docs/content/development/extensions-contrib/cassandra.md
docs/content/development/extensions-contrib/cloudfiles.md
docs/content/development/extensions-contrib/distinctcount.md
docs/content/development/extensions-contrib/google.md
docs/content/development/extensions-contrib/graphite.md
docs/content/development/extensions-contrib/influx.md
docs/content/development/extensions-contrib/kafka-emitter.md
doc

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[David Lim]

Hi Julian,

Thank you for the thorough review!

For the GPG key, my understanding is that it was expected that users would
fetch the key by either running 'gpg --import KEYS' on the KEYS file (as
per https://www.apache.org/dev/release-signing.html#keys-policy) or by
importing it from the Apache phonebook (
https://people.apache.org/keys/committer/davidlim.asc) or grabbing it from
a well-known key server (e.g.
http://pgp.mit.edu/pks/lookup?search=davidlim%40apache.org&op=index). Did
this not work for you?

> src.tar.gz file contains files such as
./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s
I will check to see whether these files are expected or not.

The files you identified from the diff against the git tag are all either
expected to be omitted or were generated as part of the source packaging.

For instructions on building the release from source, I mentioned the
command in the original post but it may have been somewhat buried. The
command I used was:

mvn clean install -Papache-release -Dtar

I'll make sure that this is updated in the docs.

As for the file exclusions, maybe the committers who helped set up the
exclusions can comment. I suspect that many of them are either a) files
which cannot properly support the licensing header and remain syntactically
valid, or b) deemed to be insignificant in its creative content and
therefore not protected by copyright law, as per:
http://www.apache.org/legal/src-headers.html#faq-exceptions.

Thanks again!

David







On Mon, Oct 22, 2018 at 9:32 PM Julian Hyde  wrote:

> -1 due to GPG error; but also see other concerns below and fix them if
> there are genuine issues.
>
> As this is Druid’s first Apache release candidate, I am impressed by how
> many things you got right.
>
> I have completely ignored bin.tar.gz. It’s not possible to “release”
> binaries in Apache because it’s not possible to audit binaries.
>
> I downloaded and checked signatures. .sha512 is ok. GPG failed with “No
> public key” error:
>
> $ gpg --verify apache-druid-0.13.0-incubating-src.tar.gz.asc
> apache-druid-0.13.0-incubating-src.tar.gz
> gpg: Signature made Sat Oct 20 20:50:20 2018 PDT
> gpg:using RSA key 58B5D669D2FFD83B37D88DF8BB64B3727183DE56
> gpg: Can't check signature: No public key
>
> src.tar.gz file contains files such as
> ./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s.
> Is this expected/good/bad?
>
> There are a few binary files in the release, e.g. index.zip,
> druid.sample.tsv.zip, wikiticker-2015-09-12-sampled.json.gz,
> indexing_service.png. Sometimes binary files are a concern, but I was able
> to inspect all of these in their respective editors.
>
> I checked the contents of src.tar.gz against git commit acf15b4. There are
> a few differences, as follows. Are any of them surprising?
>
> $ diff -r . /tmp/apache-druid-0.13.0-incubating-src/
> Only in .: .git
> Only in .: .gitignore
> Only in .: .idea
> Only in .: .travis.yml
> Only in .: eclipse.importorder
> Only in .: eclipse_formatting.xml
> Only in
> /tmp/apache-druid-0.13.0-incubating-src/extensions-core/protobuf-extensions:
> dependency-reduced-pom.xml
> Only in /tmp/apache-druid-0.13.0-incubating-src/: git.version
> Only in ./integration-tests: .gitignore
> Only in .: publications
> Only in .: upload.sh
>
> I could not find a list of instructions for how to build the source code.
> I checked README.md, CONTRIBUTING.md; there were some back-handed
> instructions in INTELLIJ_SETUP.md. In my opinion a source release should
> have instructions how to build, including a list of supported platforms
> (java versions, operating systems if applicable). As indeed should the home
> page.
>
> Built the code successfully using “mvn -DskipTests install” and Java 8 on
> macOS. There were quite a few “[WARNING]” lines.
>
> Glad to see that all .java files have headers. But quite a lot of files[1]
> do not. I saw that you added them as exclusions to apache-rat. Can you
> explain the thinking behind these exclusions?
>
> Julian
>
> [1] Files without headers
>
> $ for i in $(git ls-files | egrep -v
> 'test/resources|LICENSE|NOTICE|\.(png|pdf|zip|jpg)$'); do grep -s "Licensed
> to the Apache Software" $i >/dev/null || echo "$i"; done
> .gitignore
> .idea/inspectionProfiles/Druid.xml
> .idea/inspectionProfiles/profiles_settings.xml
> .idea/misc.xml
> .idea/scopes/NonGeneratedFiles.xml
> .idea/scopes/UnusedInspectionsScope.xml
> .travis.yml
> CONTRIBUTING.md
> DISCLAIMER
> INTELLIJ_SETUP.md
> README.md
> ci/README_TeamCity.md
> codestyle/druid-forbidden-apis.txt
> codestyle/joda-time-forbidden-apis.txt
> common/src/main/antlr4/org/apache/druid/math/expr/antlr/Expr.g4
> common/src/main/resources/services/javax.annotation.processing.Processor
> docs/_bin/deploy-docs.sh
> docs/_bin/get-milestone-contributors.py
> docs/_bin/make-redirects.py
> docs/_config.yml
> docs/_graphics/druid-dataflow-3.svg
> docs/_graphics/d

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[David Lim]

Hi Julian,

I believe the PaxHeader files are the result of extracting a tarball built
with POSIX tar with a GNU or other variant. I believe it is a result of
this configuration:
https://github.com/apache/incubator-druid/blob/master/distribution/pom.xml#L195

Does Apache have guidelines on what variant of tar should be used in
generating release artifacts?

Also, just thought I would note that we do have published documentation on
building from source here:
https://github.com/apache/incubator-druid/blob/master/docs/content/development/build.md
- but there are a few statements that should be updated, hence my comment
that I'll make sure the docs get updated.

Regards,
David


On Mon, Oct 22, 2018 at 10:20 PM David Lim  wrote:

> Hi Julian,
>
> Thank you for the thorough review!
>
> For the GPG key, my understanding is that it was expected that users would
> fetch the key by either running 'gpg --import KEYS' on the KEYS file (as
> per https://www.apache.org/dev/release-signing.html#keys-policy) or by
> importing it from the Apache phonebook (
> https://people.apache.org/keys/committer/davidlim.asc) or grabbing it
> from a well-known key server (e.g.
> http://pgp.mit.edu/pks/lookup?search=davidlim%40apache.org&op=index). Did
> this not work for you?
>
> > src.tar.gz file contains files such as
> ./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s
> I will check to see whether these files are expected or not.
>
> The files you identified from the diff against the git tag are all either
> expected to be omitted or were generated as part of the source packaging.
>
> For instructions on building the release from source, I mentioned the
> command in the original post but it may have been somewhat buried. The
> command I used was:
>
> mvn clean install -Papache-release -Dtar
>
> I'll make sure that this is updated in the docs.
>
> As for the file exclusions, maybe the committers who helped set up the
> exclusions can comment. I suspect that many of them are either a) files
> which cannot properly support the licensing header and remain syntactically
> valid, or b) deemed to be insignificant in its creative content and
> therefore not protected by copyright law, as per:
> http://www.apache.org/legal/src-headers.html#faq-exceptions.
>
> Thanks again!
>
> David
>
>
>
>
>
>
>
> On Mon, Oct 22, 2018 at 9:32 PM Julian Hyde  wrote:
>
>> -1 due to GPG error; but also see other concerns below and fix them if
>> there are genuine issues.
>>
>> As this is Druid’s first Apache release candidate, I am impressed by how
>> many things you got right.
>>
>> I have completely ignored bin.tar.gz. It’s not possible to “release”
>> binaries in Apache because it’s not possible to audit binaries.
>>
>> I downloaded and checked signatures. .sha512 is ok. GPG failed with “No
>> public key” error:
>>
>> $ gpg --verify apache-druid-0.13.0-incubating-src.tar.gz.asc
>> apache-druid-0.13.0-incubating-src.tar.gz
>> gpg: Signature made Sat Oct 20 20:50:20 2018 PDT
>> gpg:using RSA key 58B5D669D2FFD83B37D88DF8BB64B3727183DE56
>> gpg: Can't check signature: No public key
>>
>> src.tar.gz file contains files such as
>> ./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s.
>> Is this expected/good/bad?
>>
>> There are a few binary files in the release, e.g. index.zip,
>> druid.sample.tsv.zip, wikiticker-2015-09-12-sampled.json.gz,
>> indexing_service.png. Sometimes binary files are a concern, but I was able
>> to inspect all of these in their respective editors.
>>
>> I checked the contents of src.tar.gz against git commit acf15b4. There
>> are a few differences, as follows. Are any of them surprising?
>>
>> $ diff -r . /tmp/apache-druid-0.13.0-incubating-src/
>> Only in .: .git
>> Only in .: .gitignore
>> Only in .: .idea
>> Only in .: .travis.yml
>> Only in .: eclipse.importorder
>> Only in .: eclipse_formatting.xml
>> Only in
>> /tmp/apache-druid-0.13.0-incubating-src/extensions-core/protobuf-extensions:
>> dependency-reduced-pom.xml
>> Only in /tmp/apache-druid-0.13.0-incubating-src/: git.version
>> Only in ./integration-tests: .gitignore
>> Only in .: publications
>> Only in .: upload.sh
>>
>> I could not find a list of instructions for how to build the source code.
>> I checked README.md, CONTRIBUTING.md; there were some back-handed
>> instructions in INTELLIJ_SETUP.md. In my opinion a source release should
>> have instructions how to build, including a list of supported platforms
>> (java versions, operating systems if applicable). As indeed should the home
>> page.
>>
>> Built the code successfully using “mvn -DskipTests install” and Java 8 on
>> macOS. There were quite a few “[WARNING]” lines.
>>
>> Glad to see that all .java files have headers. But quite a lot of
>> files[1] do not. I saw that you added them as exclusions to apache-rat. Can
>> you explain the thinking behind these exclusions?
>>
>> Julian
>>
>> [1] Files without h

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Julian Hyde]

Your’e right. After I imported the keys, using

$ gpg --recv-keys 58B5D669D2FFD83B37D88DF8BB64B3727183DE56

it worked. I could have done ‘gpg —import KEYS’ also.

Changing my vote to +0 (binding). I would give +1 but the artifacts I am asked 
to review contains a bin.tar.gz and I have no idea how to review binary 
artifacts. Maybe some other reviewers can chime in.

I do know how to find out online how to build Druid. I think it is important 
that src.tar.gz is self-contained, and that includes the necessary build 
instructions. (Just as I really appreciate when a box of pasta has “boil for 12 
minutes” written on the side.)

I don’t know whether Apache has guidelines for PaxHeaders. I’m just saying it 
looked weird to me. And by the way, emacs tar-mode choked on the tar file. Not 
a blocker, just friction.

There is a way to add headers to .md files. And I claim there is just as much 
creativity in these as in source code. Please fix in the next release.

Julian


> On Oct 22, 2018, at 10:04 PM, David Lim  wrote:
> 
> Hi Julian,
> 
> I believe the PaxHeader files are the result of extracting a tarball built
> with POSIX tar with a GNU or other variant. I believe it is a result of
> this configuration:
> https://github.com/apache/incubator-druid/blob/master/distribution/pom.xml#L195
> 
> Does Apache have guidelines on what variant of tar should be used in
> generating release artifacts?
> 
> Also, just thought I would note that we do have published documentation on
> building from source here:
> https://github.com/apache/incubator-druid/blob/master/docs/content/development/build.md
> - but there are a few statements that should be updated, hence my comment
> that I'll make sure the docs get updated.
> 
> Regards,
> David
> 
> 
> On Mon, Oct 22, 2018 at 10:20 PM David Lim  wrote:
> 
>> Hi Julian,
>> 
>> Thank you for the thorough review!
>> 
>> For the GPG key, my understanding is that it was expected that users would
>> fetch the key by either running 'gpg --import KEYS' on the KEYS file (as
>> per https://www.apache.org/dev/release-signing.html#keys-policy) or by
>> importing it from the Apache phonebook (
>> https://people.apache.org/keys/committer/davidlim.asc) or grabbing it
>> from a well-known key server (e.g.
>> http://pgp.mit.edu/pks/lookup?search=davidlim%40apache.org&op=index). Did
>> this not work for you?
>> 
>>> src.tar.gz file contains files such as
>> ./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s
>> I will check to see whether these files are expected or not.
>> 
>> The files you identified from the diff against the git tag are all either
>> expected to be omitted or were generated as part of the source packaging.
>> 
>> For instructions on building the release from source, I mentioned the
>> command in the original post but it may have been somewhat buried. The
>> command I used was:
>> 
>> mvn clean install -Papache-release -Dtar
>> 
>> I'll make sure that this is updated in the docs.
>> 
>> As for the file exclusions, maybe the committers who helped set up the
>> exclusions can comment. I suspect that many of them are either a) files
>> which cannot properly support the licensing header and remain syntactically
>> valid, or b) deemed to be insignificant in its creative content and
>> therefore not protected by copyright law, as per:
>> http://www.apache.org/legal/src-headers.html#faq-exceptions.
>> 
>> Thanks again!
>> 
>> David
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Mon, Oct 22, 2018 at 9:32 PM Julian Hyde  wrote:
>> 
>>> -1 due to GPG error; but also see other concerns below and fix them if
>>> there are genuine issues.
>>> 
>>> As this is Druid’s first Apache release candidate, I am impressed by how
>>> many things you got right.
>>> 
>>> I have completely ignored bin.tar.gz. It’s not possible to “release”
>>> binaries in Apache because it’s not possible to audit binaries.
>>> 
>>> I downloaded and checked signatures. .sha512 is ok. GPG failed with “No
>>> public key” error:
>>> 
>>> $ gpg --verify apache-druid-0.13.0-incubating-src.tar.gz.asc
>>> apache-druid-0.13.0-incubating-src.tar.gz
>>> gpg: Signature made Sat Oct 20 20:50:20 2018 PDT
>>> gpg:using RSA key 58B5D669D2FFD83B37D88DF8BB64B3727183DE56
>>> gpg: Can't check signature: No public key
>>> 
>>> src.tar.gz file contains files such as
>>> ./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s.
>>> Is this expected/good/bad?
>>> 
>>> There are a few binary files in the release, e.g. index.zip,
>>> druid.sample.tsv.zip, wikiticker-2015-09-12-sampled.json.gz,
>>> indexing_service.png. Sometimes binary files are a concern, but I was able
>>> to inspect all of these in their respective editors.
>>> 
>>> I checked the contents of src.tar.gz against git commit acf15b4. There
>>> are a few differences, as follows. Are any of them surprising?
>>> 
>>> $ diff -r . /tmp/apache-druid-0.13.0-incubating-src/
>>> Only in .: .git
>>>

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Gian Merlino]

-1 because there are issues tagged for 0.13.0 that are not part of this
release:

- https://github.com/apache/incubator-druid/pull/6512
- https://github.com/apache/incubator-druid/pull/6514
- https://github.com/apache/incubator-druid/pull/6516
- https://github.com/apache/incubator-druid/pull/6508
- https://github.com/apache/incubator-druid/pull/6520
- https://github.com/apache/incubator-druid/issues/6546

I also noticed a doc problem that I haven't filed an issue for yet, which
is that the tutorials download section isn't accurate any longer. It says
to use http://static.druid.io/, but we probably won't put the artifacts
there. And it says to do "cd druid-#{DRUIDVERSION}" but now the directory
name is "apache-druid" not "druid".

I tried to go through an Apache style verification process anyway. Here's
what I looked at.

Source release:
- GPG signature and SHA512 are ok
- Tarball name and structure looks ok
- LICENSE, NOTICE, and DISCLAIMER are present
- Code builds and tests pass (by running "mvn package")
- Cloned a fresh Druid repo, checked out druid-0.13.0-incubating-rc1
(acf15b42778d3a84638193a3b07c6814cf2f35a2), and compared it to the source
release. The source release has two extra files: git.version (expected)
and extensions-core/protobuf-extensions/dependency-reduced-pom.xml
(unexpected). Perhaps the latter should be removed. The source release is
_missing_ a few files that I am ok with them missing, since they don't seem
to be necessary in a source release (.gitignore, .idea, .travis.yml,
eclipse.importorder, eclipse_formatting.xml, publications, upload.sh).

Binary "release" (not really a release, from what I understand, but still
important):
- GPG signature and SHA512 are ok
- Tarball name and structure looks ok. It expands to
"apache-druid-0.13.0-incubating" not "apache-druid-0.13.0-incubating-bin"
but IMO that is fine.
- Did the "tutorial-batch" quickstart and verified data could be loaded and
queried.

On Tue, Oct 23, 2018 at 11:56 AM Julian Hyde  wrote:

> Your’e right. After I imported the keys, using
>
> $ gpg --recv-keys 58B5D669D2FFD83B37D88DF8BB64B3727183DE56
>
> it worked. I could have done ‘gpg —import KEYS’ also.
>
> Changing my vote to +0 (binding). I would give +1 but the artifacts I am
> asked to review contains a bin.tar.gz and I have no idea how to review
> binary artifacts. Maybe some other reviewers can chime in.
>
> I do know how to find out online how to build Druid. I think it is
> important that src.tar.gz is self-contained, and that includes the
> necessary build instructions. (Just as I really appreciate when a box of
> pasta has “boil for 12 minutes” written on the side.)
>
> I don’t know whether Apache has guidelines for PaxHeaders. I’m just saying
> it looked weird to me. And by the way, emacs tar-mode choked on the tar
> file. Not a blocker, just friction.
>
> There is a way to add headers to .md files. And I claim there is just as
> much creativity in these as in source code. Please fix in the next release.
>
> Julian
>
>
> > On Oct 22, 2018, at 10:04 PM, David Lim  wrote:
> >
> > Hi Julian,
> >
> > I believe the PaxHeader files are the result of extracting a tarball
> built
> > with POSIX tar with a GNU or other variant. I believe it is a result of
> > this configuration:
> >
> https://github.com/apache/incubator-druid/blob/master/distribution/pom.xml#L195
> >
> > Does Apache have guidelines on what variant of tar should be used in
> > generating release artifacts?
> >
> > Also, just thought I would note that we do have published documentation
> on
> > building from source here:
> >
> https://github.com/apache/incubator-druid/blob/master/docs/content/development/build.md
> > - but there are a few statements that should be updated, hence my comment
> > that I'll make sure the docs get updated.
> >
> > Regards,
> > David
> >
> >
> > On Mon, Oct 22, 2018 at 10:20 PM David Lim  wrote:
> >
> >> Hi Julian,
> >>
> >> Thank you for the thorough review!
> >>
> >> For the GPG key, my understanding is that it was expected that users
> would
> >> fetch the key by either running 'gpg --import KEYS' on the KEYS file (as
> >> per https://www.apache.org/dev/release-signing.html#keys-policy) or by
> >> importing it from the Apache phonebook (
> >> https://people.apache.org/keys/committer/davidlim.asc) or grabbing it
> >> from a well-known key server (e.g.
> >> http://pgp.mit.edu/pks/lookup?search=davidlim%40apache.org&op=index).
> Did
> >> this not work for you?
> >>
> >>> src.tar.gz file contains files such as
> >>
> ./PaxHeaders.X/apache-druid-0.13.0-incubating-src_indexing-service_src_test_java_org_apache_druid_s
> >> I will check to see whether these files are expected or not.
> >>
> >> The files you identified from the diff against the git tag are all
> either
> >> expected to be omitted or were generated as part of the source
> packaging.
> >>
> >> For instructions on building the release from source, I mentioned the
> >> command in the original post but it may have been som

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Julian Hyde]

> On Oct 30, 2018, at 12:04 PM, Gian Merlino  wrote:
> 
> It says
> to use http://static.druid.io/, but we probably won't put the artifacts
> there.

Indeed. It is mandatory that the artifacts and their checksums are hosted on 
apache.org . (There can be mirrors.)

Julian

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[Roman Leventov]

Another issue that needs to be resolved before the release is
https://github.com/apache/incubator-druid/issues/6559

On Wed, 31 Oct 2018 at 00:12, Julian Hyde  wrote:

>
>
> > On Oct 30, 2018, at 12:04 PM, Gian Merlino  wrote:
> >
> > It says
> > to use http://static.druid.io/, but we probably won't put the artifacts
> > there.
>
> Indeed. It is mandatory that the artifacts and their checksums are hosted
> on apache.org . (There can be mirrors.)
>
> Julian
>
>

Re: [VOTE] Release Apache Druid (incubating) 0.13.0 [RC1]

[David Lim]

Hello,

Voting on this thread is now closed in favor of RC2. Please take a look at
the proposed RC2 artifacts and vote!

https://lists.apache.org/thread.html/48d595def20faeac8ac0362441a3c1d4e6af814a36b68c6d236e6be5@%3Cdev.druid.apache.org%3E



On Wed, Oct 31, 2018 at 11:47 AM Roman Leventov 
wrote:

> Another issue that needs to be resolved before the release is
> https://github.com/apache/incubator-druid/issues/6559
>
> On Wed, 31 Oct 2018 at 00:12, Julian Hyde  wrote:
>
> >
> >
> > > On Oct 30, 2018, at 12:04 PM, Gian Merlino  wrote:
> > >
> > > It says
> > > to use http://static.druid.io/, but we probably won't put the
> artifacts
> > > there.
> >
> > Indeed. It is mandatory that the artifacts and their checksums are hosted
> > on apache.org . (There can be mirrors.)
> >
> > Julian
> >
> >
>