+1

Rebuilt code, ran a local cluster with a wordcount topology. LGTM

On Sun, 3 Oct 2021 at 13:51, Alexandre Vermeerbergen <
avermeerber...@gmail.com> wrote:

> Hi,
>
> I'm surprised and glad to see a new release on Storm 1.2.x, as I have
> still not succeeded in migrating to Storm 2.x.
>  Not exactly related to this VOTE, but is there some hope to see a
> Storm 1.x release which could run with Java 17 LTS ?
>
> Indeed, we currently run our topologies with Storm 1.2.3 with Java 11
> LTS with no issue, my first attempt with Java 17 miserably fail
> because of some forbidden access to Java internals...
>
> Should I fill an JIRA for this is there's some hope for Storm 1.x fixes?
>
> Kind regards,
> Alex
>
>
> Le ven. 1 oct. 2021 à 21:19, Ethan Li <etha...@apache.org> a écrit :
> >
> > This is a call to vote on releasing Apache Storm 1.2.4 (rc1)
> >
> > Full list of changes in this release:
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/RELEASE_NOTES.html
> >
> > The tag/commit to be voted upon is v1.2.4:
> >
> >
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=1bc944091b727e9a892bb36349231fcc57d9ea30
> >
> > The source archive being voted upon can be found here:
> >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-1.2.4-rc1/apache-storm-1.2.4-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.4-rc1/
> >
> > The release artifacts are signed with the following key:
> >
> > https://www.apache.org/dist/storm/KEYS
> >
> > The Nexus staging repository for this release is:
> >
> > https://repository.apache.org/content/repositories/orgapachestorm-1099
> >
> > Please vote on releasing this package as Apache Storm 1.2.4.
> >
> > 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.4
> > [ ]  0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
>

Reply via email to