Re: Storm 2.5.0 Release Candidate Vote

2023-08-07 Thread Nikhil Singh
 Hi Bipin,+1 from me too [non binding]. I was able to run the unit tests and wc 
topology.
Thank you,-Nikhil
On Monday, August 7, 2023 at 04:37:30 PM CDT, Aaron Gresch 
 wrote:  
 
 I am +1 for RC4.

I was able to build and run all unit tests.
I downloaded the release and ran a word count topology successfully.



On Thu, Aug 3, 2023 at 4:41 PM Bipin Prasad  wrote:

> Storm Release candidate version 2.5.0 rc4 is here:
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
> Please vote on this release.
>
>    1. How to vote is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>    2. Release notes are here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
>    .
>    3. The tag/commit to be voted upon is v2.5.0:
>    4. The source archive being votes upon is here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
>    5. The release artifacts are signed with the following key:
>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> in
>    this file https://www.apache.org/dist/storm/KEYS
>
>
> 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.5.0
>    [ ]  0 No opinion
>    [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> --Bipin Prasad
>
> On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad 
> wrote:
>
> > Storm Release candidate version 2.5.0 rc3 is here:
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> > Please vote on this release.
> >
> >    1. How to vote is described here:
> >
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >    2. Release notes are here:
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
> >    .
> >    3. The tag/commit to be voted upon is v2.5.0:
> >    4. The source archive being votes upon is here:
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
> >    5. The release artifacts are signed with the following key:
> >
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> >    in this file https://www.apache.org/dist/storm/KEYS
> >
> >
> > 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.5.0
> >    [ ]  0 No opinion
> >    [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > --Bipin Prasad
> >
> > On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad 
> > wrote:
> >
> >> Storm Release candidate version 2.5.0 rc2 is here:
> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> >> Please vote on this release.
> >>
> >>    1. How to vote is described here:
> >>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >>    2. Release notes are here:
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
> >>    .
> >>    3. The tag/commit to be voted upon is v2.5.0:
> >>    4. The source archive being votes upon is here:
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> >>    5. The release artifacts are signed with the following key:
> >>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> >>    in this file https://www.apache.org/dist/storm/KEYS
> >>
> >>
> >> 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.5.0
> >>    [ ]  0 No opinion
> >>    [ ] -1 Do not release this package because...
> >>
> >> Thanks to everyone who contributed to this release.
> >>
> >> --Bipin Prasad
> >>
> >> On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad 
> >> wrote:
> >>
> >>> Storm Release candidate version 2.5.0 rc1 is here:
> >>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> >>> Please vote on this release.
> >>>
> >>>    1. How to vote is described here:
> >>>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >>>    2. Release notes are here:
> >>>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> >>>    .
> >>>    3. The tag/commit to be voted upon is v2.5.0:
> >>>    4. The source archive being votes upon is here:
> >>>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> >>>    5. The release artifacts are signed with the following key:
> >>>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> >>>    in this file 

Re: Storm 2.5.0 Release Candidate Vote

2023-08-07 Thread Aaron Gresch
I am +1 for RC4.

I was able to build and run all unit tests.
I downloaded the release and ran a word count topology successfully.



On Thu, Aug 3, 2023 at 4:41 PM Bipin Prasad  wrote:

> Storm Release candidate version 2.5.0 rc4 is here:
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4
> Please vote on this release.
>
>1. How to vote is described here:
>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
>2. Release notes are here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/RELEASE_NOTES.html
>.
>3. The tag/commit to be voted upon is v2.5.0:
>4. The source archive being votes upon is here:
>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc4/apache-storm-2.5.0-src.tar.gz
>5. The release artifacts are signed with the following key:
>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> in
>this file https://www.apache.org/dist/storm/KEYS
>
>
> 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.5.0
> [ ]   0 No opinion
> [ ] -1 Do not release this package because...
>
> Thanks to everyone who contributed to this release.
>
> --Bipin Prasad
>
> On Wed, Aug 2, 2023 at 4:07 PM Bipin Prasad 
> wrote:
>
> > Storm Release candidate version 2.5.0 rc3 is here:
> > https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3
> > Please vote on this release.
> >
> >1. How to vote is described here:
> >
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >2. Release notes are here:
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/RELEASE_NOTES.html
> >.
> >3. The tag/commit to be voted upon is v2.5.0:
> >4. The source archive being votes upon is here:
> >
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc3/apache-storm-2.5.0-src.tar.gz
> >5. The release artifacts are signed with the following key:
> >
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> > in this file https://www.apache.org/dist/storm/KEYS
> >
> >
> > 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.5.0
> > [ ]   0 No opinion
> > [ ] -1 Do not release this package because...
> >
> > Thanks to everyone who contributed to this release.
> >
> > --Bipin Prasad
> >
> > On Tue, Jul 25, 2023 at 8:28 AM Bipin Prasad 
> > wrote:
> >
> >> Storm Release candidate version 2.5.0 rc2 is here:
> >> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2
> >> Please vote on this release.
> >>
> >>1. How to vote is described here:
> >>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >>2. Release notes are here:
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/RELEASE_NOTES.html
> >>.
> >>3. The tag/commit to be voted upon is v2.5.0:
> >>4. The source archive being votes upon is here:
> >>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc2/apache-storm-2.5.0-src.tar.gz
> >>5. The release artifacts are signed with the following key:
> >>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> >> in this file https://www.apache.org/dist/storm/KEYS
> >>
> >>
> >> 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.5.0
> >> [ ]   0 No opinion
> >> [ ] -1 Do not release this package because...
> >>
> >> Thanks to everyone who contributed to this release.
> >>
> >> --Bipin Prasad
> >>
> >> On Mon, Jun 26, 2023 at 4:15 PM Bipin Prasad 
> >> wrote:
> >>
> >>> Storm Release candidate version 2.5.0 rc1 is here:
> >>> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1
> >>> Please vote on this release.
> >>>
> >>>1. How to vote is described here:
> >>>
> https://github.com/apache/storm/blob/master/RELEASING.md#how-to-vote-on-a-release-candidate
> >>>2. Release notes are here:
> >>>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/RELEASE_NOTES.html
> >>>.
> >>>3. The tag/commit to be voted upon is v2.5.0:
> >>>4. The source archive being votes upon is here:
> >>>
> https://dist.apache.org/repos/dist/dev/storm/apache-storm-2.5.0-rc1/apache-storm-2.5.0-src.tar.gz
> >>>5. The release artifacts are signed with the following key:
> >>>
> https://keyserver.ubuntu.com/pks/lookup?op=get=0x134716af768d9b6e
> >>> in this file https://www.apache.org/dist/storm/KEYS
> >>>
> >>>
> >>> When voting, please list the actions taken to verify the release.
> >>> This vote will be open for at least 72 hours.
> >>>
> 

Re: [PR] [STORM-3938] Unhandled InterruptedException and missing log in Supervisor's close(… (storm)

2023-08-07 Thread via GitHub


rzo1 commented on PR #3554:
URL: https://github.com/apache/storm/pull/3554#issuecomment-1667646679

   Can you rebase @LoggingResearch 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] [STORM-3939] Remove gitact build for JDK 8, set class format to JDK11 and allow introspection in test (storm)

2023-08-07 Thread via GitHub


rzo1 merged PR #3558:
URL: https://github.com/apache/storm/pull/3558


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@storm.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: Addendum to Storm's release process

2023-08-07 Thread Richard Zowalla
Hi Alexandre,

from a formal point of view: I guess, that you are still in a "pending"
state, so everything is ok (no need to re-cast, etc.). 

I just asked our PMC chair to formally provide you with the information
you need for your ASF id, CLA etc.

Gruß
Richard



Am Montag, dem 07.08.2023 um 08:44 +0200 schrieb Alexandre
Vermeerbergen:
> Hello,
> 
> Ah sorry: I indeed accepted Richard's invitation to join as a PMC,
> but I
> thought I had to wait for some formal confirmation before I could
> cast a
> binding vote - hence my mention as "non-binding " with my vote.
> 
> Should I recast it, or I am right to wait for some formal annouce of
> my PMC
> status?
> 
> Alexandre
> 
> 
> 
> Le sam. 5 août 2023, 19:16, Richard Zowalla  a
> écrit :
> 
> > Hey Bipin,
> > 
> > think it is sufficient, if you put your own +1 to the original
> > thread.
> > Given that Alexandre has also accepted his invitation, we should be
> > good
> > now.
> > 
> > Thanks for doing the release!
> > 
> > Gruß
> > Richard
> > 
> > 
> > 
> > 
> > Am 5. August 2023 19:09:40 MESZ schrieb Bipin Prasad <
> > bipinpra...@apache.org>:
> > > Richard,
> > >    Thanks for this note on the vote process. I will ask for
> > > further
> > votes on the to ensure compliance - even though RC4 was moved to
> > release
> > area. Will send out an email with the new locations. Once an
> > additional
> > vote is registered, I will send out the vote result email.
> > > 
> > > --Bipin
> > > 
> > > On 2023/08/04 20:05:35 Richard Zowalla wrote:
> > > > Hi all,
> > > > 
> > > > 
> > > > During the last release vote, I noticed the following things
> > > > that we
> > > > should do better next time to adhere to the ASF release
> > > > guidelines
> > > > [1,2,3]:
> > > > 
> > > > - We need at least 3 (binding) votes for a release. A binding
> > > > vote
> > > > originates from PMC members only (although community is
> > > > encouraged to
> > > > also cast non-binding votes and test the binaries). For 2.5.0,
> > > > we only
> > > > had 2 (binding) votes for RC4 and an implicit one (at least I
> > > > assume
> > > > it) by our release manager, which would need to be cast next
> > > > time, so
> > > > we can formally do the release according to the foundation's
> > > > policies.
> > > > 
> > > > - A successful vote should be followed by a [VOTE] [RESULT]
> > > > mail to
> > > > indicate, that the vote was successful and the release process
> > > > continues.
> > > > 
> > > > - If multiple RC's are needed to do a release, we would need to
> > > > sent a
> > > > mail with [VOTE] [CANCELLED] to indicate the failed attempt and
> > > > start a
> > > > new mail thread with the next release candidate. This make the
> > > > process
> > > > more transparent to everyone.
> > > > 
> > > > No blaming, just my observation. I think, that we can do better
> > > > next
> > > > time :)
> > > > 
> > > > Gruß
> > > > Richard
> > > > 
> > > > [1] https://infra.apache.org/release-publishing.html
> > > > [2] https://www.apache.org/legal/release-policy.html
> > > > [3] https://www.apache.org/foundation/voting.html
> > > > 
> > 



Re: Addendum to Storm's release process

2023-08-07 Thread Alexandre Vermeerbergen
Hello,

Ah sorry: I indeed accepted Richard's invitation to join as a PMC, but I
thought I had to wait for some formal confirmation before I could cast a
binding vote - hence my mention as "non-binding " with my vote.

Should I recast it, or I am right to wait for some formal annouce of my PMC
status?

Alexandre



Le sam. 5 août 2023, 19:16, Richard Zowalla  a écrit :

> Hey Bipin,
>
> think it is sufficient, if you put your own +1 to the original thread.
> Given that Alexandre has also accepted his invitation, we should be good
> now.
>
> Thanks for doing the release!
>
> Gruß
> Richard
>
>
>
>
> Am 5. August 2023 19:09:40 MESZ schrieb Bipin Prasad <
> bipinpra...@apache.org>:
> >Richard,
> >Thanks for this note on the vote process. I will ask for further
> votes on the to ensure compliance - even though RC4 was moved to release
> area. Will send out an email with the new locations. Once an additional
> vote is registered, I will send out the vote result email.
> >
> >--Bipin
> >
> >On 2023/08/04 20:05:35 Richard Zowalla wrote:
> >> Hi all,
> >>
> >>
> >> During the last release vote, I noticed the following things that we
> >> should do better next time to adhere to the ASF release guidelines
> >> [1,2,3]:
> >>
> >> - We need at least 3 (binding) votes for a release. A binding vote
> >> originates from PMC members only (although community is encouraged to
> >> also cast non-binding votes and test the binaries). For 2.5.0, we only
> >> had 2 (binding) votes for RC4 and an implicit one (at least I assume
> >> it) by our release manager, which would need to be cast next time, so
> >> we can formally do the release according to the foundation's policies.
> >>
> >> - A successful vote should be followed by a [VOTE] [RESULT] mail to
> >> indicate, that the vote was successful and the release process
> >> continues.
> >>
> >> - If multiple RC's are needed to do a release, we would need to sent a
> >> mail with [VOTE] [CANCELLED] to indicate the failed attempt and start a
> >> new mail thread with the next release candidate. This make the process
> >> more transparent to everyone.
> >>
> >> No blaming, just my observation. I think, that we can do better next
> >> time :)
> >>
> >> Gruß
> >> Richard
> >>
> >> [1] https://infra.apache.org/release-publishing.html
> >> [2] https://www.apache.org/legal/release-policy.html
> >> [3] https://www.apache.org/foundation/voting.html
> >>
>