I am voting -1 on this release. Everything was fine with the build till I started testing the docker image. The issue is described here - https://github.com/apache/druid/pull/17347 I am -1 because the upgrade can break clusters running the official Apache Druid docker image.
On Mon, Oct 14, 2024 at 7:58 AM Kashif Faraz <kfa...@apache.org> wrote: > Hi all, > > I have created a build for Apache Druid 31.0.0, release candidate 1. > > Thanks to everyone who has helped contribute to the release! You can read > the proposed release notes here: > https://github.com/apache/druid/issues/17332 > > The release candidate has been tagged in GitHub as > druid-31.0.0-rc1 (479b0680ba1c79e5d0d2dc9c640457d0210612f6), > available here: > https://github.com/apache/druid/releases/tag/druid-31.0.0-rc1 > > The artifacts to be voted on are located here: > https://dist.apache.org/repos/dist/dev/druid/31.0.0-rc1/ > > A staged Maven repository is available for review at: > https://repository.apache.org/content/repositories/orgapachedruid-1072/ > > Staged druid.apache.org website documentation is available here: > https://druid.staged.apache.org/docs/31.0.0/design/index.html > > A Docker image containing the binary of the release candidate can be > retrieved via: > docker pull apache/druid:31.0.0-rc1 > > artifact checksums > src: > > 8b54da2c354515eecbd638355b1b04f856d01dbbdabbde44d12ac1c1f4c224d63a1be6617c37f630ad5c81b1a1c40171138c7b5edcfada082ec6b585b2d10ece > bin: > > 5dd32e72c3cccd630fdd851ff3ff0881781bbaaa1bc82f2f2a8d8d32e98f4b85c648f790566fc2da8aed372714fc3bcea395e8084186dbd8f5efcf0b8a9fdbda > docker: b16d95238d5919e17316d30f673c9280d236a34397eee927cccc83d58ffbda95 > > Release artifacts are signed with the following key: > https://people.apache.org/keys/committer/kfaraz.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/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-31.0.0-src.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-31.0.0-src.tar.gz.sha512 ; echo) > > diff <(shasum -a512 apache-druid-31.0.0-bin.tar.gz | \ > cut -d ' ' -f1) \ > <(cat apache-druid-31.0.0-bin.tar.gz.sha512 ; echo) > > Verify signatures: > gpg --verify apache-druid-31.0.0-src.tar.gz.asc \ > apache-druid-31.0.0-src.tar.gz > > gpg --verify apache-druid-31.0.0-bin.tar.gz.asc \ > apache-druid-31.0.0-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. > > [ ] +1 Release this package as Apache Druid 31.0.0 > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > > Thanks > Kashif Faraz >
