In the vote email I said the vote would be open for at least 72 hours. Obviously it's been open for longer than that but to give more time for testing I plan to leave it open until Thursday. Then, assuming all goes well, I'll plan to complete the release on Friday (15th/16th Feb).
Ideally we would like 2/3 of PMC members to vote. Even if you don't have time to do any testing, please vote - I think there is already good feedback from testing to give you enough to decide how to vote. I've created issues for problems found so far: https://issues.apache.org/jira/browse/BROOKLYN-632 https://issues.apache.org/jira/browse/BROOKLYN-633 https://issues.apache.org/jira/browse/BROOKLYN-634 Thanks Duncan On Tue, 13 Feb 2024 at 09:35, Duncan Grant <duncan.gr...@cloudsoft.io> wrote: > > This thread is for discussions related to the release vote. > > I should clarify what we are looking for in a release vote. Particularly, > we are looking for people to download,validate, and test the release. > Only if you are satisfied that the artifacts are correct and the quality is > high enough, should you make a "+1" vote. Alongside your vote you should > list > the checks that you made. > > The vote is not simply about "the master branch contains the features I > wanted" - > it is about making sure that *these* artifacts are *correct* (e.g. they are > not corrupted, hashes and signatures pass) and are of *sufficiently high > quality* to be stamped as an official release of The Apache Software > Foundation. > > Why test the artifacts when master is looking good? Here are some reasons: > > - somebody could have made a commit that broke it, since you last git > pulled > - the release branch could have been made at the wrong point, or > inconsistently > between all of the submodules > - something in the release process could have broken it > - I could have made a mistake and corrupted the files > - a problem with the Apache infrastructure could mean that the release > files are > unobtainable or corrupted > > This is why the release manager needs you to download the actual release > artifacts and try them out. > > The way Apache works can be a bit arcane sometimes, but it's all done with > a reason. If the vote passes then the contents of the email and its links > become "endorsed" by The Apache Software Foundation, and the Foundation > will > take on legal liability for them, forever. > > And of course we want the best possible experience for our users - so we > need > the actual release files to be tested manually to make sure that a mistake > does > not ruin the experience for users. > > So if you can spare an hour or more to download some of the artifacts and > try > them out, then it will be *very* useful! The vote lasts for three days so > there's no need to rush to get a vote in. > > Thanks! > > Duncan > > On Fri, 2 Feb 2024 at 09:52, Duncan Grant <duncangr...@gmail.com> wrote: > >> This is to call for a vote for the release of Apache Brooklyn 1.1.0. >> >> This release comprises of a source code distribution, and a corresponding >> binary distribution, and Maven artifacts. >> >> The source and binary distributions, including signatures, digests, etc. >> can >> be found at: >> >> >> https://dist.apache.org/repos/dist/dev/brooklyn/apache-brooklyn-1.1.0-rc1 >> >> The artifact SHA-256 checksums are as follows: >> >> 7e9f516888cd449b4336b490a1a61f2ad38e043f780e89287aa66c4f8372638e >> *apache-brooklyn-1.1.0-rc1-1.noarch.rpm >> 0444355d282e997d45b78c1db2917e6868c7406cd4a4f32e5687dc61c6911665 >> *apache-brooklyn-1.1.0-rc1-bin.tar.gz >> 68a8bafbc08da9e1098fe9b62862347fdeb3f5eb126b7ff324ca8ac7e19c2d19 >> *apache-brooklyn-1.1.0-rc1-bin.zip >> 9e3ec65c85823d577e8ba2e52245f4f8a79e21fdab9fe2e491c0292315b8feb8 >> *apache-brooklyn-1.1.0-rc1-classic.tar.gz >> 1f26e6344dd87e0fc4044fbdcf4a9dfeb82bab0ada0ebebed6d9efade13a09d7 >> *apache-brooklyn-1.1.0-rc1-classic.zip >> 2b1624321e867b2b2953aa20b9a30d3c81594f2bf3d62cb977879dd21bab6289 >> *apache-brooklyn-1.1.0-rc1-client-cli-linux.tar.gz >> 8eee13fd6f1112df4e2e7019e1891acd1fc01fe539fb34a7c910c3bb2c057810 >> *apache-brooklyn-1.1.0-rc1-client-cli-linux.zip >> 164d15fbdad43442529080e2cbfd740b5af7699403e1ab474fe9881eeb52a4d4 >> *apache-brooklyn-1.1.0-rc1-client-cli-macosx.tar.gz >> 851ff58cadb7dac8c5cd329c345c7ec6dce0c6fff58b843681b1dc82ceabd0e6 >> *apache-brooklyn-1.1.0-rc1-client-cli-macosx.zip >> 0fcd3e47a526a47c1b746b6a033876618a05d45c0e1da79514ad86e405b155dd >> *apache-brooklyn-1.1.0-rc1-client-cli-windows.tar.gz >> 0f7717763b29be671f666bfa017665f205d803e14d8f68407502c1c4ac2f93cb >> *apache-brooklyn-1.1.0-rc1-client-cli-windows.zip >> ee35a63a93a16da651145585c5679289cac40f92a5a57b18cf38273fef620cc5 >> *apache-brooklyn-1.1.0-rc1-src.tar.gz >> e8d5d51bb94f76b346e769389751bd6c5fef4321fd02b3dd3b009598d5718a09 >> *apache-brooklyn-1.1.0-rc1-src.zip >> 3bc9bae54819ad8b3d4c3b2166d829a75082cf667d3e47fe7445d879b306c98f >> *apache-brooklyn-1.1.0-rc1-vagrant.tar.gz >> 6ea928ade39e9e4b08a37b6bd6dd3ce2fb68417bf1f3c04d063d18aa3ba63a7a >> *apache-brooklyn-1.1.0-rc1-vagrant.zip >> 955d0e1d77daa1663a34dda1294244394bddc6333a7e352a04648ec0fc7ccf28 >> *apache-brooklyn-1.1.0-rc1.deb >> >> The Nexus staging repository for the Maven artifacts is located at: >> >> >> https://repository.apache.org/content/repositories/orgapachebrooklyn-1056 >> >> All release artifacts are signed with the following key: >> >> https://people.apache.org/keys/committer/duncangrant.asc >> >> KEYS file available here: >> >> https://dist.apache.org/repos/dist/release/brooklyn/KEYS >> >> >> The artifacts were built from git commit IDs: >> >> brooklyn: 83141598299c145d971461e9b103ea5298efe66d >> -n brooklyn-client: >> 587d869822666a6ea8ca80043d33c198acdf8326 >> -n brooklyn-dist: >> bab76db9d4d5ae646cd1fb43fd59ce909bf047ac >> -n brooklyn-docs: >> e0aae5c49e0e55128ade90ef21d5022ed6e79878 >> -n brooklyn-library: >> cdcb3195228a3c4bc8f1031e7a54012ad02237fd >> -n brooklyn-server: >> bb3d2ec8de376837b63a6a9742f3ccbbfd69ac38 >> -n brooklyn-ui: >> c8f7c5869652aba403d6a1e5f743d3e5393774eb >> All of the above have been tagged as "apache-brooklyn-1.1.0-rc1" >> >> Please vote on releasing this package as Apache Brooklyn 1.1.0. >> >> The vote will be open for at least 72 hours. >> [ ] +1 Release this package as Apache Brooklyn 1.1.0 >> [ ] +0 no opinion >> [ ] -1 Do not release this package because ... >> >> >> Thanks! >> >> >> >> CHECKLIST for reference >> >> [ ] Download links work. >> [ ] Binaries work. >> [ ] Checksums and PGP signatures are valid. >> [ ] Expanded source archive matches contents of RC tag. >> [ ] Expanded source archive builds and passes tests. >> [ ] LICENSE is present and correct. >> [ ] NOTICE is present and correct, including copyright date. >> [ ] All files have license headers where appropriate. >> [ ] All dependencies have compatible licenses. >> [ ] No compiled archives bundled in source archive. >> [ ] I follow this project’s commits list. >> > > > -- > > Duncan Grant > > Lead Software Engineer E: duncan.gr...@cloudsoft.io > > www.cloudsoft.io Connect with me on LinkedIn > <https://www.linkedin.com/in/duncan-grant-3605901/> > > <https://bit.ly/3P8xWL8> > > Advanced automation to auto-remediate and reduce toil > Use this website link: www.cloudsoft.io <https://bit.ly/3P8xWL8> > -- Duncan Grant Lead Software Engineer E: duncan.gr...@cloudsoft.io www.cloudsoft.io Connect with me on LinkedIn <https://www.linkedin.com/in/duncan-grant-3605901/> <https://bit.ly/3P8xWL8> Advanced automation to auto-remediate and reduce toil Use this website link: www.cloudsoft.io <https://bit.ly/3P8xWL8>
