Are we waiting for https://github.com/apache/storm/pull/2538 to start the next RC ?
This patch seem to contain more changes than just fixing a logging issue. Can we only address the concern raised about logs filling with WARN messages and address the rest in the next release or does the logs indicate some bug which is a blocker for 1.2.0 ? - Arun On 1/29/18, 12:30 PM, "P. Taylor Goetz" <ptgo...@gmail.com> wrote: >Cancelling this RC in order to address Stig’s concerns. > >-Taylor > >> On Jan 26, 2018, at 4:11 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote: >> >> This is a call to vote on releasing Apache Storm 1.2.0 (rc2) >> >> Full list of changes in this release: >> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc2/RELEASE_NOTES.html >> >> The tag/commit to be voted upon is v1.2.0: >> >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=tree;h=17a4645d7d65f5a7a08a50b5185c0fc52e82692f;hb=458aa1cb696097cf07d4466aa7417c7b89662221 >> >> The source archive being voted upon can be found here: >> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc2/apache-storm-1.2.0-src.tar.gz >> >> Other release files, signatures and digests can be found here: >> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.0-rc2/ >> >> The release artifacts are signed with the following key: >> >> https://git-wip-us.apache.org/repos/asf?p=storm.git;a=blob_plain;f=KEYS;hb=22b832708295fa2c15c4f3c70ac0d2bc6fded4bd >> >> The Nexus staging repository for this release is: >> >> https://repository.apache.org/content/repositories/orgapachestorm-1056 >> >> Please vote on releasing this package as Apache Storm 1.2.0. >> >> When voting, please list the actions taken to verify the release. >> >> This vote will be open for at least 72 hours. >> >> [ ] +1 Release this package as Apache Storm 1.2.0 >> [ ] 0 No opinion >> [ ] -1 Do not release this package because... >> >> Thanks to everyone who contributed to this release. >> >> -Taylor >
