Found a pretty ugly bug with the new 'auto' stuff so am going to cancel this vote and make an RC2
On Sat, May 13, 2023 at 1:56 PM Clint Wylie <cwy...@apache.org> wrote: > > I forgot to mention that I had to refresh the expiration on my gpg key > (I think I did everything correctly), but I am unsure if voters might > need to get the updated keys on their side for stuff to validate > correctly. > > On Fri, May 12, 2023 at 1:07 PM Clint Wylie <cwy...@apache.org> wrote: > > > > FYI when running build with -Pwebsite i ran into some issues with the > > vulnerability checker, but didn't think they needed to be blockers for > > the RC vote (especially since the website can be updated > > independently). I will be investigating these to ensure they are not a > > concern for us. > > > > Speaking of the website, there are a couple more doc only changes I am > > aware of that will be backported to the 26 release branch, and I will > > update the staging website once they are merged. > > > > On Fri, May 12, 2023 at 12:39 PM Clint Wylie <cwy...@apache.org> wrote: > > > > > > Hi all, > > > > > > I have created a build for Apache Druid 26.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/14064 > > > > > > The release candidate has been tagged in GitHub as > > > druid-26.0.0-rc1 (bb58a23aedccc7f2bf4484d5211c936cfd90038a), > > > available here: > > > https://github.com/apache/druid/releases/tag/druid-26.0.0-rc1 > > > > > > The artifacts to be voted on are located here: > > > https://dist.apache.org/repos/dist/dev/druid/26.0.0-rc1/ > > > > > > A staged Maven repository is available for review at: > > > https://repository.apache.org/content/repositories/orgapachedruid-1040/ > > > > > > Staged druid.apache.org website documentation is available here: > > > https://druid.staged.apache.org/docs/26.0.0/design/index.html > > > > > > A Docker image containing the binary of the release candidate can be > > > retrieved via: > > > docker pull apache/druid:26.0.0-rc1 > > > > > > artifact checksums > > > src: > > > a9483a1f4bcb9a921f98d3a6a0815a2c20c218a8d64b9743f1f14b1b3d7bc2a9220ac7fc5d4fa9572a3973ab40214ed9f527f53d2f6ff401c5bbdee72105c02a > > > bin: > > > e40d8644e1546000a27ff0af61f2f3200606af719623ecf8db9a517f8f5c3e54660385a7a99e7cc50eea5a32e4348c58b00b2b89bbab44eeeeb97cc59b24b44f > > > hadoop3-bin: > > > 12a8fa196a7dcf252d08b7b73e1117a25efc8de49a74a653dd51631a4fc91d53e4fc6d82df3c375142b0c3fa6f2007446f1beb5f680fdbda5510f2ebb7a9bfd3 > > > docker: > > > 54b0037966884f66aafc426fdd236b237b96885c3a76608f4cf497d8f3369a5c > > > > > > 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/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-26.0.0-src.tar.gz | \ > > > cut -d ' ' -f1) \ > > > <(cat apache-druid-26.0.0-src.tar.gz.sha512 ; echo) > > > > > > diff <(shasum -a512 apache-druid-26.0.0-bin.tar.gz | \ > > > cut -d ' ' -f1) \ > > > <(cat apache-druid-26.0.0-bin.tar.gz.sha512 ; echo) > > > > > > diff <(shasum -a512 apache-druid-26.0.0-hadoop3-bin.tar.gz | \ > > > cut -d ' ' -f1) \ > > > <(cat apache-druid-26.0.0-hadoop3-bin.tar.gz.sha512 ; echo) > > > > > > Verify signatures: > > > gpg --verify apache-druid-26.0.0-src.tar.gz.asc \ > > > apache-druid-26.0.0-src.tar.gz > > > > > > gpg --verify apache-druid-26.0.0-bin.tar.gz.asc \ > > > apache-druid-26.0.0-bin.tar.gz > > > > > > gpg --verify apache-druid-26.0.0-hadoop3-bin.tar.gz.asc \ > > > apache-druid-26.0.0-hadoop3-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 26.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! --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
