Closing this release thread as I'm about to open the vote on the next
thread.

On Mon, 8 Jun 2020 at 11:09, Kishorkumar Patil <[email protected]>
wrote:

> Hi Govid/Ethan,
>
> Since the patch https://github.com/apache/storm/pull/3280 is merged, can
> we
> create the next release candidate?
>
> -Kishor
>
> On Fri, Jun 5, 2020 at 8:12 AM Julien Nioche <
> [email protected]>
> wrote:
>
> > That's great thanks Ethan
> >
> > On Thu, 4 Jun 2020 at 19:02, Ethan Li <[email protected]> wrote:
> >
> > > The fix is ready. Please review
> > https://github.com/apache/storm/pull/3280
> > > <https://github.com/apache/storm/pull/3280>
> > >
> > > > On Jun 4, 2020, at 11:34 AM, Kishorkumar Patil <
> > [email protected]>
> > > wrote:
> > > >
> > > > Hi Julian,
> > > >
> > > > I agree with you on this. Ethan has a fix that will resolve both
> these
> > > > issues. We should get the change in and cut another RC.
> > > >
> > > > -Kishor
> > > >
> > > >
> > > > On Thu, Jun 4, 2020 at 12:23 PM Julien Nioche <
> > > [email protected]>
> > > > wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> Great to see that there has been some work on Storm 2 recently but I
> > am
> > > >> afraid I'll have to cast a (non-binding) -1 because of STORM-3620
> > > >> <https://issues.apache.org/jira/browse/STORM-3620> and STORM-3582
> > > >> <https://issues.apache.org/jira/projects/STORM/issues/STORM-3582>.
> > > >>
> > > >> I have tried to get StormCrawler to work with Storm 2.x but the
> issues
> > > >> above have prevented me from doing so. At least one other person has
> > had
> > > >> the same problems as you can see in the JIRAs above.
> > > >>
> > > >> I think these are serious issues and they should be addressed in the
> > > next
> > > >> release. I would be very happy to help if I can.
> > > >>
> > > >> Julien
> > > >>
> > > >> On Thu, 4 Jun 2020 at 00:00, Govind Menon <[email protected]>
> wrote:
> > > >>
> > > >>> This is a call to vote on releasing Apache Storm 2.2.0 (As a
> personal
> > > >> note
> > > >>> I would like to thank P. Taylor Goetz and Ethan Li for all the
> > > >>> documentation they have set up to make releasing easier)
> > > >>>
> > > >>> Full list of changes in this release:
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/RELEASE_NOTES.html
> > > >>>
> > > >>> The tag/commit to be voted upon is v2.2.0:
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://gitbox.apache.org/repos/asf?p=storm.git;a=commit;h=6326b0c783c0025440c629e17653c0c7577f27e6
> > > >>>
> > > >>> The source archive being voted upon can be found here:
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > >
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.2.0/apache-storm-2.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-2.2.0/
> > > >>>
> > > >>> 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-1091
> > > >>>
> > > >>> Please vote on releasing this package as Apache Storm 2.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 2.2.0
> > > >>> [ ]  0 No opinion
> > > >>> [ ] -1 Do not release this package because...
> > > >>>
> > > >>> Thanks to everyone who contributed to this release.
> > > >>>
> > > >>
> > > >>
> > > >> --
> > > >>
> > > >> *Open Source Solutions for Text Engineering*
> > > >>
> > > >> http://www.digitalpebble.com
> > > >> http://digitalpebble.blogspot.com/
> > > >> #digitalpebble <http://twitter.com/digitalpebble>
> > > >>
> > >
> > >
> >
> > --
> >
> > *Open Source Solutions for Text Engineering*
> >
> > http://www.digitalpebble.com
> > http://digitalpebble.blogspot.com/
> > #digitalpebble <http://twitter.com/digitalpebble>
> >
>

Reply via email to