Hi,

here is my +1 (binding).

- Checked the signatures of the source files.
- Build from source.
- Did some tests with our topologies in local / distributed mode.

Thanks for preparing.

Gruß
Richard

On 2025/07/26 15:18:52 Rui Abreu wrote:
> Hi folks,
> 
> I have posted a 1st release candidate for the Apache Storm 2.8.2
> release and it is ready for testing.
> 
> The Nexus staging repository is here:
>     https://repository.apache.org/content/repositories/orgapachestorm-1119
> 
> Storm Source and Binary Release with sha512 signature files are here:
>     https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.8.2-rc1/
> The release artifacts are signed with the following key:
> 
> https://keyserver.ubuntu.com/pks/lookup?op=index&fingerprint=on&search=rabreu
>     in this file https://www.apache.org/dist/storm/KEYS
> 
> The release was made from the Apache Storm 2.8.2 tag at:
>     https://github.com/apache/storm/tree/v2.8.2
> 
> Full list of changes in this release:
> 
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.8.2-rc1/RELEASE_NOTES.html
> 
> To use it in a maven build set the version for Storm to 2.8.2 and add
> the following URL to your settings.xml file:
> https://repository.apache.org/content/repositories/orgapachestorm-1119
> 
> The release was made using the Storm release process, documented on
> the GitHub repository:
> https://github.com/apache/storm/blob/master/RELEASING.md
> 
> Please vote on releasing these packages as Apache Storm 2.8.2. The
> vote is open for at least the next 72 hours.
> "How to vote" is described here:
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> When voting, please list the actions taken to verify the release.
> 
> Only votes from the Storm PMC are binding, but everyone is welcome to
> check the release candidate and vote.
> The vote passes if at least three binding +1 votes are cast.
> 
> [ ] +1 Release this package as Apache Storm [VERSION]
> [ ]  0 No opinion
> [ ] -1 Do not release this package because...
> 
> Thanks to everyone who contributed to this release.
> 

Reply via email to