Re: [PROPOSE] RM for 4.19.0
On Wed, May 3, 2023 at 12:01 PM Abhishek Kumar wrote: > Daan, Rohit and others, > > Personally, I don't see log4j2 PR alone or one particular feature/PR that > can be the reason for managing the release. Though I certainly understand > it may create some additional work for the RM. > I definitely agree with you on that, Abhishek. But whether you or Daniel is the RM, we still need to conclude in aggreement on this point before we can think of a release in my opinion. For users (and maybe to a lesser degree to operators) it might not seem as a big functional change, but it going be *a* defining feature for developers. Since Daniel also has an interest in being the RM for the 4.19 release, is > happy to do that additional work and RM work is not the most exciting work > for me :-P, I'm happy to support Daniel for the role. I, like others, can > help him where I can. > > Regards, > Abhishek > > > On Wed, 3 May 2023 at 14:49, Rohit Yadav > wrote: > > > +1 > > > > Thanks for volunteering Abhishek. As you've worked already as a RM for > > CloudStack LTS maintenance releases that you've shared and I think you > have > > all the necessary experience to work as the 4.19 RM. > > > > Daan, I don't see any mention of log4j on this thread or feel that > > Abhishek has disregarded the log4j issue. As an individual contributor, > > he's well within his rights to volunteer as a release manager and share > his > > opinion and thoughts in the community in this or any other threads. > > > > We shouldn't force or expect anybody to conclude a discussion in a way we > > would want. We must all conduct and treat one another professionally and > > politely on the mailing lists [1]. > > > > [1] https://cloudstack.apache.org/mailing-lists.html > > > > > > Regards. > > > > > > From: Daan Hoogland > > Sent: Tuesday, May 2, 2023 13:19 > > To: dev@cloudstack.apache.org > > Cc: us...@cloudstack.apache.org > > Subject: Re: [PROPOSE] RM for 4.19.0 > > > > Abhishek, I think the discussion about log4j2 needs to be concluded in > > coercion with this. I am fine if you and/or Daniel co-RM this release for > > instance, but the log4j issue may not be disregarded on these grounds and > > must be fully discussed and agreed upon. > > > > On Tue, May 2, 2023 at 9:43 AM Suresh Kumar Anaparti < > > sureshkumar.anapa...@gmail.com> wrote: > > > > > +1, Good luck Abhishek! > > > > > > Regards, > > > Suresh > > > > > > On Mon, May 1, 2023 at 7:49 PM Boris Stoyanov > > > wrote: > > > > > > > > +1, thanks Abhishek. I know we’re in safe hands with you! > > > > > > > > Bobby. > > > > > > > > From: Harikrishna Patnala > > > > Date: Monday, 1 May 2023, 9:21 > > > > To: us...@cloudstack.apache.org , > > > dev@cloudstack.apache.org > > > > Subject: Re: [PROPOSE] RM for 4.19.0 > > > > +1, thanks for volunteering and good luck Abhishek. > > > > > > > > Regards, > > > > Harikrishna > > > > > > > > From: Abhishek Kumar > > > > Date: Sunday, 30 April 2023 at 10:23 PM > > > > To: dev@cloudstack.apache.org , > > > us...@cloudstack.apache.org > > > > Subject: [PROPOSE] RM for 4.19.0 > > > > Dear All, > > > > > > > > I would like to propose and put myself forward as the release manager > > > for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and > co-RM'd a > > > couple of releases before that. I would like to take experiences from > > those > > > to work on a successful release. > > > > > > > > I propose we start early, sometime in Q3 2023, with the planning, > > > triaging, bug-fixing, etc to get back on the traditional two-release > per > > > year cycle. With this we can aim to cut the RC sometime in October. I > > will > > > propose a detailed timeline soon. > > > > > > > > I hope to have your support. Please let me know if you have any > > > thoughts/comments. > > > > > > > > Regards, > > > > Abhishek > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > Daan > > > > > > > > > -- Daan
Re: [PROPOSE] RM for 4.19.0
On Wed, May 3, 2023 at 11:19 AM Rohit Yadav wrote: > +1 > > Thanks for volunteering Abhishek. As you've worked already as a RM for > CloudStack LTS maintenance releases that you've shared and I think you have > all the necessary experience to work as the 4.19 RM. > > Daan, I don't see any mention of log4j on this thread or feel that > Abhishek has disregarded the log4j issue. As an individual contributor, > he's well within his rights to volunteer as a release manager and share his > opinion and thoughts in the community in this or any other threads. > Sorry if I wasn't clear, there is no mention of log4j on this thread, but there is mention of RM work on the log4j thread [2]. [2] https://lists.apache.org/thread/t62rp2pzsrl21vjlqbdgg49kmdxgjxgd I am not saying that either Daniel or Abhishek should be the RM, but the work that we are going to have should be agreed upon. Having two RM candidates is a luxury we should not squander. If they can join efforts and get to a mutual supported plan that would be ideal. We shouldn't force or expect anybody to conclude a discussion in a way we > would want. We must all conduct and treat one another professionally and > politely on the mailing lists [1]. > > [1] https://cloudstack.apache.org/mailing-lists.html In short, I stand by my previous mail on this thread. This is provided there is no misunderstanding on what was meant. > > > > Regards. > > > From: Daan Hoogland > Sent: Tuesday, May 2, 2023 13:19 > To: dev@cloudstack.apache.org > Cc: us...@cloudstack.apache.org > Subject: Re: [PROPOSE] RM for 4.19.0 > > Abhishek, I think the discussion about log4j2 needs to be concluded in > coercion with this. I am fine if you and/or Daniel co-RM this release for > instance, but the log4j issue may not be disregarded on these grounds and > must be fully discussed and agreed upon. > > > ... > > > -- > Daan > > > > -- Daan
Re: [PROPOSE] RM for 4.19.0
Daan, Rohit and others, Personally, I don't see log4j2 PR alone or one particular feature/PR that can be the reason for managing the release. Though I certainly understand it may create some additional work for the RM. Since Daniel also has an interest in being the RM for the 4.19 release, is happy to do that additional work and RM work is not the most exciting work for me :-P, I'm happy to support Daniel for the role. I, like others, can help him where I can. Regards, Abhishek On Wed, 3 May 2023 at 14:49, Rohit Yadav wrote: > +1 > > Thanks for volunteering Abhishek. As you've worked already as a RM for > CloudStack LTS maintenance releases that you've shared and I think you have > all the necessary experience to work as the 4.19 RM. > > Daan, I don't see any mention of log4j on this thread or feel that > Abhishek has disregarded the log4j issue. As an individual contributor, > he's well within his rights to volunteer as a release manager and share his > opinion and thoughts in the community in this or any other threads. > > We shouldn't force or expect anybody to conclude a discussion in a way we > would want. We must all conduct and treat one another professionally and > politely on the mailing lists [1]. > > [1] https://cloudstack.apache.org/mailing-lists.html > > > Regards. > > > From: Daan Hoogland > Sent: Tuesday, May 2, 2023 13:19 > To: dev@cloudstack.apache.org > Cc: us...@cloudstack.apache.org > Subject: Re: [PROPOSE] RM for 4.19.0 > > Abhishek, I think the discussion about log4j2 needs to be concluded in > coercion with this. I am fine if you and/or Daniel co-RM this release for > instance, but the log4j issue may not be disregarded on these grounds and > must be fully discussed and agreed upon. > > On Tue, May 2, 2023 at 9:43 AM Suresh Kumar Anaparti < > sureshkumar.anapa...@gmail.com> wrote: > > > +1, Good luck Abhishek! > > > > Regards, > > Suresh > > > > On Mon, May 1, 2023 at 7:49 PM Boris Stoyanov > > wrote: > > > > > > +1, thanks Abhishek. I know we’re in safe hands with you! > > > > > > Bobby. > > > > > > From: Harikrishna Patnala > > > Date: Monday, 1 May 2023, 9:21 > > > To: us...@cloudstack.apache.org , > > dev@cloudstack.apache.org > > > Subject: Re: [PROPOSE] RM for 4.19.0 > > > +1, thanks for volunteering and good luck Abhishek. > > > > > > Regards, > > > Harikrishna > > > > > > From: Abhishek Kumar > > > Date: Sunday, 30 April 2023 at 10:23 PM > > > To: dev@cloudstack.apache.org , > > us...@cloudstack.apache.org > > > Subject: [PROPOSE] RM for 4.19.0 > > > Dear All, > > > > > > I would like to propose and put myself forward as the release manager > > for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a > > couple of releases before that. I would like to take experiences from > those > > to work on a successful release. > > > > > > I propose we start early, sometime in Q3 2023, with the planning, > > triaging, bug-fixing, etc to get back on the traditional two-release per > > year cycle. With this we can aim to cut the RC sometime in October. I > will > > propose a detailed timeline soon. > > > > > > I hope to have your support. Please let me know if you have any > > thoughts/comments. > > > > > > Regards, > > > Abhishek > > > > > > > > > > > > > > > > > > > > > > > > > > -- > Daan > > > >
Re: [PROPOSE] RM for 4.19.0
+1 Thanks for volunteering Abhishek. As you've worked already as a RM for CloudStack LTS maintenance releases that you've shared and I think you have all the necessary experience to work as the 4.19 RM. Daan, I don't see any mention of log4j on this thread or feel that Abhishek has disregarded the log4j issue. As an individual contributor, he's well within his rights to volunteer as a release manager and share his opinion and thoughts in the community in this or any other threads. We shouldn't force or expect anybody to conclude a discussion in a way we would want. We must all conduct and treat one another professionally and politely on the mailing lists [1]. [1] https://cloudstack.apache.org/mailing-lists.html Regards. From: Daan Hoogland Sent: Tuesday, May 2, 2023 13:19 To: dev@cloudstack.apache.org Cc: us...@cloudstack.apache.org Subject: Re: [PROPOSE] RM for 4.19.0 Abhishek, I think the discussion about log4j2 needs to be concluded in coercion with this. I am fine if you and/or Daniel co-RM this release for instance, but the log4j issue may not be disregarded on these grounds and must be fully discussed and agreed upon. On Tue, May 2, 2023 at 9:43 AM Suresh Kumar Anaparti < sureshkumar.anapa...@gmail.com> wrote: > +1, Good luck Abhishek! > > Regards, > Suresh > > On Mon, May 1, 2023 at 7:49 PM Boris Stoyanov > wrote: > > > > +1, thanks Abhishek. I know we’re in safe hands with you! > > > > Bobby. > > > > From: Harikrishna Patnala > > Date: Monday, 1 May 2023, 9:21 > > To: us...@cloudstack.apache.org , > dev@cloudstack.apache.org > > Subject: Re: [PROPOSE] RM for 4.19.0 > > +1, thanks for volunteering and good luck Abhishek. > > > > Regards, > > Harikrishna > > > > From: Abhishek Kumar > > Date: Sunday, 30 April 2023 at 10:23 PM > > To: dev@cloudstack.apache.org , > us...@cloudstack.apache.org > > Subject: [PROPOSE] RM for 4.19.0 > > Dear All, > > > > I would like to propose and put myself forward as the release manager > for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a > couple of releases before that. I would like to take experiences from those > to work on a successful release. > > > > I propose we start early, sometime in Q3 2023, with the planning, > triaging, bug-fixing, etc to get back on the traditional two-release per > year cycle. With this we can aim to cut the RC sometime in October. I will > propose a detailed timeline soon. > > > > I hope to have your support. Please let me know if you have any > thoughts/comments. > > > > Regards, > > Abhishek > > > > > > > > > > > > > > > -- Daan
Re: [PROPOSE] RM for 4.19.0
Abhishek, I think the discussion about log4j2 needs to be concluded in coercion with this. I am fine if you and/or Daniel co-RM this release for instance, but the log4j issue may not be disregarded on these grounds and must be fully discussed and agreed upon. On Tue, May 2, 2023 at 9:43 AM Suresh Kumar Anaparti < sureshkumar.anapa...@gmail.com> wrote: > +1, Good luck Abhishek! > > Regards, > Suresh > > On Mon, May 1, 2023 at 7:49 PM Boris Stoyanov > wrote: > > > > +1, thanks Abhishek. I know we’re in safe hands with you! > > > > Bobby. > > > > From: Harikrishna Patnala > > Date: Monday, 1 May 2023, 9:21 > > To: us...@cloudstack.apache.org , > dev@cloudstack.apache.org > > Subject: Re: [PROPOSE] RM for 4.19.0 > > +1, thanks for volunteering and good luck Abhishek. > > > > Regards, > > Harikrishna > > > > From: Abhishek Kumar > > Date: Sunday, 30 April 2023 at 10:23 PM > > To: dev@cloudstack.apache.org , > us...@cloudstack.apache.org > > Subject: [PROPOSE] RM for 4.19.0 > > Dear All, > > > > I would like to propose and put myself forward as the release manager > for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a > couple of releases before that. I would like to take experiences from those > to work on a successful release. > > > > I propose we start early, sometime in Q3 2023, with the planning, > triaging, bug-fixing, etc to get back on the traditional two-release per > year cycle. With this we can aim to cut the RC sometime in October. I will > propose a detailed timeline soon. > > > > I hope to have your support. Please let me know if you have any > thoughts/comments. > > > > Regards, > > Abhishek > > > > > > > > > > > > > > > -- Daan
Re: [PROPOSE] RM for 4.19.0
+1, Good luck Abhishek! Regards, Suresh On Mon, May 1, 2023 at 7:49 PM Boris Stoyanov wrote: > > +1, thanks Abhishek. I know we’re in safe hands with you! > > Bobby. > > From: Harikrishna Patnala > Date: Monday, 1 May 2023, 9:21 > To: us...@cloudstack.apache.org , > dev@cloudstack.apache.org > Subject: Re: [PROPOSE] RM for 4.19.0 > +1, thanks for volunteering and good luck Abhishek. > > Regards, > Harikrishna > > From: Abhishek Kumar > Date: Sunday, 30 April 2023 at 10:23 PM > To: dev@cloudstack.apache.org , > us...@cloudstack.apache.org > Subject: [PROPOSE] RM for 4.19.0 > Dear All, > > I would like to propose and put myself forward as the release manager for > 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple > of releases before that. I would like to take experiences from those to work > on a successful release. > > I propose we start early, sometime in Q3 2023, with the planning, triaging, > bug-fixing, etc to get back on the traditional two-release per year cycle. > With this we can aim to cut the RC sometime in October. I will propose a > detailed timeline soon. > > I hope to have your support. Please let me know if you have any > thoughts/comments. > > Regards, > Abhishek > > > > > > >
Re: [PROPOSE] RM for 4.19.0
+1, thanks Abhishek. I know we’re in safe hands with you! Bobby. From: Harikrishna Patnala Date: Monday, 1 May 2023, 9:21 To: us...@cloudstack.apache.org , dev@cloudstack.apache.org Subject: Re: [PROPOSE] RM for 4.19.0 +1, thanks for volunteering and good luck Abhishek. Regards, Harikrishna From: Abhishek Kumar Date: Sunday, 30 April 2023 at 10:23 PM To: dev@cloudstack.apache.org , us...@cloudstack.apache.org Subject: [PROPOSE] RM for 4.19.0 Dear All, I would like to propose and put myself forward as the release manager for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple of releases before that. I would like to take experiences from those to work on a successful release. I propose we start early, sometime in Q3 2023, with the planning, triaging, bug-fixing, etc to get back on the traditional two-release per year cycle. With this we can aim to cut the RC sometime in October. I will propose a detailed timeline soon. I hope to have your support. Please let me know if you have any thoughts/comments. Regards, Abhishek
Re: [PROPOSE] RM for 4.19.0
+1, thanks for volunteering and good luck Abhishek. Regards, Harikrishna From: Abhishek Kumar Date: Sunday, 30 April 2023 at 10:23 PM To: dev@cloudstack.apache.org , us...@cloudstack.apache.org Subject: [PROPOSE] RM for 4.19.0 Dear All, I would like to propose and put myself forward as the release manager for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple of releases before that. I would like to take experiences from those to work on a successful release. I propose we start early, sometime in Q3 2023, with the planning, triaging, bug-fixing, etc to get back on the traditional two-release per year cycle. With this we can aim to cut the RC sometime in October. I will propose a detailed timeline soon. I hope to have your support. Please let me know if you have any thoughts/comments. Regards, Abhishek
[PROPOSE] RM for 4.19.0
Dear All, I would like to propose and put myself forward as the release manager for 4.19.0 release. In the past, I've RM'd 4.17.1.0 release and co-RM'd a couple of releases before that. I would like to take experiences from those to work on a successful release. I propose we start early, sometime in Q3 2023, with the planning, triaging, bug-fixing, etc to get back on the traditional two-release per year cycle. With this we can aim to cut the RC sometime in October. I will propose a detailed timeline soon. I hope to have your support. Please let me know if you have any thoughts/comments. Regards, Abhishek
