Re: [DISCUSS] Calcite Release Managers
Please put me down for 1.38. > On Mar 25, 2023, at 3:06 AM, Stamatis Zampetakis wrote: > > Thanks Sergey and Benchao for volunteering. > > So far we have: > > 1.35.0 Duan Xiong > 1.36.0 Benchao Li > 1.37.0 Sergey Nuyanzin > 1.38.0 > 1.39.0 > > Regarding the timing we would like to release every 2-3 months but the > exact dates are most of the time flexible. It's up to the release manager > to start the "Towards Calcite 1.X.Y" thread and propose the dates more > convenient to them. > > Best, > Stamatis > > On Tue, Mar 21, 2023, 10:52 AM Sergey Nuyanzin wrote: > >> Thanks for the starting discussion Stamatis, >> >> depending on timeline of releases I would volunteer to help here with one >> of them >> >> On Tue, Mar 21, 2023 at 10:32 AM Benchao Li wrote: >> >>> As I've said in another ML thread[1], I will volunteer to do one. >>> >>> [1] https://lists.apache.org/thread/dcf6o3mdzflh7brsklgoy7fd1njy8jjz >>> >>> Stamatis Zampetakis 于2023年3月21日周二 17:01写道： >>> Hi everyone, In the last year or so we had the following people helping out with releasing Calcite. 1.30.0 Liya Fan 1.31.0 Adrei Sereda 1.32.0 Julian Hyde 1.33.0 Jess Balint 1.34.0 Stamatis Zampetakis Big thanks to everyone! Now we should see who can help out with the next releases. @Duan Xiong: Are you still available for 1.35.0? Any other volunteers for 1.36.0 to 1.39.0? 1.35.0 Duan Xiong 1.36.0 1.37.0 1.38.0 1.39.0 Best, Stamatis >>> >>> >>> -- >>> >>> Best, >>> Benchao Li >>> >> >> >> -- >> Best regards, >> Sergey >>
Re: [DISCUSS] Calcite Release Managers
Thanks Sergey and Benchao for volunteering. So far we have: 1.35.0 Duan Xiong 1.36.0 Benchao Li 1.37.0 Sergey Nuyanzin 1.38.0 1.39.0 Regarding the timing we would like to release every 2-3 months but the exact dates are most of the time flexible. It's up to the release manager to start the "Towards Calcite 1.X.Y" thread and propose the dates more convenient to them. Best, Stamatis On Tue, Mar 21, 2023, 10:52 AM Sergey Nuyanzin wrote: > Thanks for the starting discussion Stamatis, > > depending on timeline of releases I would volunteer to help here with one > of them > > On Tue, Mar 21, 2023 at 10:32 AM Benchao Li wrote: > > > As I've said in another ML thread[1], I will volunteer to do one. > > > > [1] https://lists.apache.org/thread/dcf6o3mdzflh7brsklgoy7fd1njy8jjz > > > > Stamatis Zampetakis 于2023年3月21日周二 17:01写道： > > > > > Hi everyone, > > > > > > In the last year or so we had the following people helping out with > > > releasing Calcite. > > > > > > 1.30.0 Liya Fan > > > 1.31.0 Adrei Sereda > > > 1.32.0 Julian Hyde > > > 1.33.0 Jess Balint > > > 1.34.0 Stamatis Zampetakis > > > > > > Big thanks to everyone! > > > > > > Now we should see who can help out with the next releases. > > > > > > @Duan Xiong: Are you still available for 1.35.0? > > > Any other volunteers for 1.36.0 to 1.39.0? > > > > > > 1.35.0 Duan Xiong > > > 1.36.0 > > > 1.37.0 > > > 1.38.0 > > > 1.39.0 > > > > > > Best, > > > Stamatis > > > > > > > > > -- > > > > Best, > > Benchao Li > > > > > -- > Best regards, > Sergey >
Re: [DISCUSS] Calcite Release Managers
Thanks for the starting discussion Stamatis, depending on timeline of releases I would volunteer to help here with one of them On Tue, Mar 21, 2023 at 10:32 AM Benchao Li wrote: > As I've said in another ML thread[1], I will volunteer to do one. > > [1] https://lists.apache.org/thread/dcf6o3mdzflh7brsklgoy7fd1njy8jjz > > Stamatis Zampetakis 于2023年3月21日周二 17:01写道： > > > Hi everyone, > > > > In the last year or so we had the following people helping out with > > releasing Calcite. > > > > 1.30.0 Liya Fan > > 1.31.0 Adrei Sereda > > 1.32.0 Julian Hyde > > 1.33.0 Jess Balint > > 1.34.0 Stamatis Zampetakis > > > > Big thanks to everyone! > > > > Now we should see who can help out with the next releases. > > > > @Duan Xiong: Are you still available for 1.35.0? > > Any other volunteers for 1.36.0 to 1.39.0? > > > > 1.35.0 Duan Xiong > > 1.36.0 > > 1.37.0 > > 1.38.0 > > 1.39.0 > > > > Best, > > Stamatis > > > > > -- > > Best, > Benchao Li > -- Best regards, Sergey
Re: [DISCUSS] Calcite Release Managers
As I've said in another ML thread[1], I will volunteer to do one. [1] https://lists.apache.org/thread/dcf6o3mdzflh7brsklgoy7fd1njy8jjz Stamatis Zampetakis 于2023年3月21日周二 17:01写道： > Hi everyone, > > In the last year or so we had the following people helping out with > releasing Calcite. > > 1.30.0 Liya Fan > 1.31.0 Adrei Sereda > 1.32.0 Julian Hyde > 1.33.0 Jess Balint > 1.34.0 Stamatis Zampetakis > > Big thanks to everyone! > > Now we should see who can help out with the next releases. > > @Duan Xiong: Are you still available for 1.35.0? > Any other volunteers for 1.36.0 to 1.39.0? > > 1.35.0 Duan Xiong > 1.36.0 > 1.37.0 > 1.38.0 > 1.39.0 > > Best, > Stamatis > -- Best, Benchao Li
[DISCUSS] Calcite Release Managers
Hi everyone, In the last year or so we had the following people helping out with releasing Calcite. 1.30.0 Liya Fan 1.31.0 Adrei Sereda 1.32.0 Julian Hyde 1.33.0 Jess Balint 1.34.0 Stamatis Zampetakis Big thanks to everyone! Now we should see who can help out with the next releases. @Duan Xiong: Are you still available for 1.35.0? Any other volunteers for 1.36.0 to 1.39.0? 1.35.0 Duan Xiong 1.36.0 1.37.0 1.38.0 1.39.0 Best, Stamatis
Re: [DISCUSS] Release Managers
Thanks everyone! Here is the list filled in for future reference: 1.30.0 Liya Fan 1.31.0 Andrei Sereda (switched with Liya) 1.32.0 Jess Balint 1.33.0 Julian Hyde 1.34.0 Duan Xiong Best, Stamatis On Fri, Feb 25, 2022 at 2:07 AM xiong duan wrote: > Hi Stamatis, >I can release the 1.34 > > Julian Hyde 于2022年2月25日周五 05:59写道： > > > Put me down for 1.33 > > > > On Thu, Feb 24, 2022 at 7:39 AM Jess Balint wrote: > > > > > > Hi Stamatis, > > > > > > I can do 1.32.0 (or whatever makes sense). > > > > > > Jess > > > > > > On Thu, Feb 24, 2022 at 5:11 AM Stamatis Zampetakis > > > > wrote: > > > > > > > Hi all, > > > > > > > > In the last 2 years or so we had the following people helping out > with > > > > releasing Calcite. > > > > > > > > 1.22.0 Danny Chan > > > > 1.23.0 Haisheng Yuan > > > > 1.24.0 Chunwei Lei > > > > 1.25.0 Andrei Sereda > > > > 1.26.0 Ruben Quesada Lopez > > > > 1.27.0 Stamatis Zampetakis > > > > 1.28.0 Julian Hyde > > > > 1.29.0 Rui Wang > > > > > > > > Big thanks to everyone! > > > > > > > > Now we should see who can help out with the next releases. Any > > volunteers > > > > for 1.32.0 to 1.34.0? > > > > > > > > 1.30.0 Andrei Seread > > > > 1.31.0 Liya Fan > > > > 1.32.0 > > > > 1.33.0 > > > > 1.34.0 > > > > > > > > Best, > > > > Stamatis > > > > > > >
Re: [DISCUSS] Release Managers
Hi Stamatis, I can release the 1.34 Julian Hyde 于2022年2月25日周五 05:59写道： > Put me down for 1.33 > > On Thu, Feb 24, 2022 at 7:39 AM Jess Balint wrote: > > > > Hi Stamatis, > > > > I can do 1.32.0 (or whatever makes sense). > > > > Jess > > > > On Thu, Feb 24, 2022 at 5:11 AM Stamatis Zampetakis > > wrote: > > > > > Hi all, > > > > > > In the last 2 years or so we had the following people helping out with > > > releasing Calcite. > > > > > > 1.22.0 Danny Chan > > > 1.23.0 Haisheng Yuan > > > 1.24.0 Chunwei Lei > > > 1.25.0 Andrei Sereda > > > 1.26.0 Ruben Quesada Lopez > > > 1.27.0 Stamatis Zampetakis > > > 1.28.0 Julian Hyde > > > 1.29.0 Rui Wang > > > > > > Big thanks to everyone! > > > > > > Now we should see who can help out with the next releases. Any > volunteers > > > for 1.32.0 to 1.34.0? > > > > > > 1.30.0 Andrei Seread > > > 1.31.0 Liya Fan > > > 1.32.0 > > > 1.33.0 > > > 1.34.0 > > > > > > Best, > > > Stamatis > > > >
Re: [DISCUSS] Release Managers
Put me down for 1.33 On Thu, Feb 24, 2022 at 7:39 AM Jess Balint wrote: > > Hi Stamatis, > > I can do 1.32.0 (or whatever makes sense). > > Jess > > On Thu, Feb 24, 2022 at 5:11 AM Stamatis Zampetakis > wrote: > > > Hi all, > > > > In the last 2 years or so we had the following people helping out with > > releasing Calcite. > > > > 1.22.0 Danny Chan > > 1.23.0 Haisheng Yuan > > 1.24.0 Chunwei Lei > > 1.25.0 Andrei Sereda > > 1.26.0 Ruben Quesada Lopez > > 1.27.0 Stamatis Zampetakis > > 1.28.0 Julian Hyde > > 1.29.0 Rui Wang > > > > Big thanks to everyone! > > > > Now we should see who can help out with the next releases. Any volunteers > > for 1.32.0 to 1.34.0? > > > > 1.30.0 Andrei Seread > > 1.31.0 Liya Fan > > 1.32.0 > > 1.33.0 > > 1.34.0 > > > > Best, > > Stamatis > >
Re: [DISCUSS] Release Managers
Hi Stamatis, I can do 1.32.0 (or whatever makes sense). Jess On Thu, Feb 24, 2022 at 5:11 AM Stamatis Zampetakis wrote: > Hi all, > > In the last 2 years or so we had the following people helping out with > releasing Calcite. > > 1.22.0 Danny Chan > 1.23.0 Haisheng Yuan > 1.24.0 Chunwei Lei > 1.25.0 Andrei Sereda > 1.26.0 Ruben Quesada Lopez > 1.27.0 Stamatis Zampetakis > 1.28.0 Julian Hyde > 1.29.0 Rui Wang > > Big thanks to everyone! > > Now we should see who can help out with the next releases. Any volunteers > for 1.32.0 to 1.34.0? > > 1.30.0 Andrei Seread > 1.31.0 Liya Fan > 1.32.0 > 1.33.0 > 1.34.0 > > Best, > Stamatis >
[DISCUSS] Release Managers
Hi all, In the last 2 years or so we had the following people helping out with releasing Calcite. 1.22.0 Danny Chan 1.23.0 Haisheng Yuan 1.24.0 Chunwei Lei 1.25.0 Andrei Sereda 1.26.0 Ruben Quesada Lopez 1.27.0 Stamatis Zampetakis 1.28.0 Julian Hyde 1.29.0 Rui Wang Big thanks to everyone! Now we should see who can help out with the next releases. Any volunteers for 1.32.0 to 1.34.0? 1.30.0 Andrei Seread 1.31.0 Liya Fan 1.32.0 1.33.0 1.34.0 Best, Stamatis
Re: [DISCUSS] Release Managers
I volunteered for 1.30 but happy to release a different version. On Fri, Jun 4, 2021 at 6:53 PM Haisheng Yuan wrote: > Thanks, Rui. > > Now we have release managers: > Rui Wang for 1.29.0 > Liya Fan for 1.30.0 > > Thanks, > Haisheng Yuan > > On 2021/06/04 22:05:34, Rui Wang wrote: > > In another related thread I volunteered for releasing 1.29.0. I think I > can > > still do it. > > > > > > -Rui > > > > On Thu, Jun 3, 2021 at 7:09 PM Fan Liya wrote: > > > > > Hi Haisheng, > > > > > > I am interested in volunteering. > > > > > > Best, > > > Liya Fan > > > > > > On Fri, Jun 4, 2021 at 6:50 AM Julian Hyde > wrote: > > > > > > > Yes, I am release manager for 1.28. I’ll aim to release first week of > > > > August. > > > > > > > > Somewhat related to the call for release managers: we need active > > > > committers. (Stamatis, can you run your stats on PRs and active > > > > committers?) On May 21, I noted that PR backlog is building up, and > > > > appealed for 5 committers to look at 5 PRs each. But since then only > 2 > > > PRs > > > > have been committed (thanks Ruben & Stamatis). We need to do better. > > > > > > > > Julian > > > > > > > > > > > > > On Jun 3, 2021, at 3:33 PM, Haisheng Yuan > wrote: > > > > > > > > > > Hi all, > > > > > > > > > > In the next half year, I hope we can get back to the pace of > release > > > for > > > > every 2 months. We need more release managers for the next few > releases, > > > is > > > > there any one interested in volunteering to be release manager? > > > > > Currently Julian is the release manager for 1.28.0, we need 3 more > for > > > > 1.29.0 ~ 1.31.0. > > > > > > > > > > Thanks, > > > > > Haisheng Yuan > > > > > > > > > > > > > >
Re: [DISCUSS] Release Managers
Thanks, Rui. Now we have release managers: Rui Wang for 1.29.0 Liya Fan for 1.30.0 Thanks, Haisheng Yuan On 2021/06/04 22:05:34, Rui Wang wrote: > In another related thread I volunteered for releasing 1.29.0. I think I can > still do it. > > > -Rui > > On Thu, Jun 3, 2021 at 7:09 PM Fan Liya wrote: > > > Hi Haisheng, > > > > I am interested in volunteering. > > > > Best, > > Liya Fan > > > > On Fri, Jun 4, 2021 at 6:50 AM Julian Hyde wrote: > > > > > Yes, I am release manager for 1.28. I’ll aim to release first week of > > > August. > > > > > > Somewhat related to the call for release managers: we need active > > > committers. (Stamatis, can you run your stats on PRs and active > > > committers?) On May 21, I noted that PR backlog is building up, and > > > appealed for 5 committers to look at 5 PRs each. But since then only 2 > > PRs > > > have been committed (thanks Ruben & Stamatis). We need to do better. > > > > > > Julian > > > > > > > > > > On Jun 3, 2021, at 3:33 PM, Haisheng Yuan wrote: > > > > > > > > Hi all, > > > > > > > > In the next half year, I hope we can get back to the pace of release > > for > > > every 2 months. We need more release managers for the next few releases, > > is > > > there any one interested in volunteering to be release manager? > > > > Currently Julian is the release manager for 1.28.0, we need 3 more for > > > 1.29.0 ~ 1.31.0. > > > > > > > > Thanks, > > > > Haisheng Yuan > > > > > > > > >
Re: [DISCUSS] Release Managers
In another related thread I volunteered for releasing 1.29.0. I think I can still do it. -Rui On Thu, Jun 3, 2021 at 7:09 PM Fan Liya wrote: > Hi Haisheng, > > I am interested in volunteering. > > Best, > Liya Fan > > On Fri, Jun 4, 2021 at 6:50 AM Julian Hyde wrote: > > > Yes, I am release manager for 1.28. I’ll aim to release first week of > > August. > > > > Somewhat related to the call for release managers: we need active > > committers. (Stamatis, can you run your stats on PRs and active > > committers?) On May 21, I noted that PR backlog is building up, and > > appealed for 5 committers to look at 5 PRs each. But since then only 2 > PRs > > have been committed (thanks Ruben & Stamatis). We need to do better. > > > > Julian > > > > > > > On Jun 3, 2021, at 3:33 PM, Haisheng Yuan wrote: > > > > > > Hi all, > > > > > > In the next half year, I hope we can get back to the pace of release > for > > every 2 months. We need more release managers for the next few releases, > is > > there any one interested in volunteering to be release manager? > > > Currently Julian is the release manager for 1.28.0, we need 3 more for > > 1.29.0 ~ 1.31.0. > > > > > > Thanks, > > > Haisheng Yuan > > > > >
Re: [DISCUSS] Release Managers
Hi Haisheng, I am interested in volunteering. Best, Liya Fan On Fri, Jun 4, 2021 at 6:50 AM Julian Hyde wrote: > Yes, I am release manager for 1.28. I’ll aim to release first week of > August. > > Somewhat related to the call for release managers: we need active > committers. (Stamatis, can you run your stats on PRs and active > committers?) On May 21, I noted that PR backlog is building up, and > appealed for 5 committers to look at 5 PRs each. But since then only 2 PRs > have been committed (thanks Ruben & Stamatis). We need to do better. > > Julian > > > > On Jun 3, 2021, at 3:33 PM, Haisheng Yuan wrote: > > > > Hi all, > > > > In the next half year, I hope we can get back to the pace of release for > every 2 months. We need more release managers for the next few releases, is > there any one interested in volunteering to be release manager? > > Currently Julian is the release manager for 1.28.0, we need 3 more for > 1.29.0 ~ 1.31.0. > > > > Thanks, > > Haisheng Yuan > >
Re: [DISCUSS] Release Managers
Yes, I am release manager for 1.28. I’ll aim to release first week of August. Somewhat related to the call for release managers: we need active committers. (Stamatis, can you run your stats on PRs and active committers?) On May 21, I noted that PR backlog is building up, and appealed for 5 committers to look at 5 PRs each. But since then only 2 PRs have been committed (thanks Ruben & Stamatis). We need to do better. Julian > On Jun 3, 2021, at 3:33 PM, Haisheng Yuan wrote: > > Hi all, > > In the next half year, I hope we can get back to the pace of release for > every 2 months. We need more release managers for the next few releases, is > there any one interested in volunteering to be release manager? > Currently Julian is the release manager for 1.28.0, we need 3 more for 1.29.0 > ~ 1.31.0. > > Thanks, > Haisheng Yuan
[DISCUSS] Release Managers
Hi all, In the next half year, I hope we can get back to the pace of release for every 2 months. We need more release managers for the next few releases, is there any one interested in volunteering to be release manager? Currently Julian is the release manager for 1.28.0, we need 3 more for 1.29.0 ~ 1.31.0. Thanks, Haisheng Yuan
Re: [DISCUSS] Release Managers
That’s reasonable, we did make many changes in year 2020. Hope the good news for 2021. Julian Hyde 于2021年2月8日 周一上午2:17写道： > Release 2.0 is largely symbolic. We develop Calcite incrementally, so it’s > more important that there are regular releases, and that they are backwards > compatible (within reason), than what those releases are called. > > That said, a major release would be an opportunity to get rid of the cruft > (deprecated APIs) that have built up over the years. We should do one at > some point in 2021. > > Julian > > > > On Feb 6, 2021, at 6:31 PM, Danny Chan wrote: > > > > Just curious, when does Calcit plan to release 2.0, there are so many > small > > versions now ~ Do we really need to be 1.3x.0 or 1.4x.0 version ? > > > > Andrei Sereda 于2021年2月5日周五 上午2:34写道： > > > >> I'm happy to help with 1.30 > >> > >> On Thu, Feb 4, 2021 at 1:27 PM Julian Hyde wrote: > >> > >>> Yes, I'll be release manager for 1.28. > >>> > >>> I think I promised to be a release manager a while ago. I forget which > >>> release. Sorry about that. > >>> > >>> On Thu, Feb 4, 2021 at 1:09 AM Stamatis Zampetakis > >>> wrote: > > That would be great Rui, thanks for volunteering. So far we have: > > 1.27 Stamatis > 1.28 Julian ? > 1.29 Rui > > It would be nice to also plan for 1.30 & 1.31 just to be a bit ahead > of > time. Are there other people willing to help? > > Best, > Stamatis > > > On Wed, Feb 3, 2021 at 12:32 AM Rui Wang > wrote: > > > I can also help on releasing (haven't done one for Calcite). > > > > > > -Rui > > > > On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde > >> wrote: > > > >> I haven't been RM for a while. I'll do 1.27, then Stamatis can do > >>> 1.28. > >> > >> On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis < > >>> zabe...@gmail.com> > >> wrote: > >>> > >>> Depending on the timing I can possibly get 1.27.0 or 1.28.0. > >>> > >>> Best, > >>> Stamatis > >>> > >>> On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan > > wrote: > >>> > Thanks for volunteering, Ruben! I think you can be the release > > manager > >> for > 1.26.0. > > We still need 2 more volunteers for the next 2 versions. > > Thanks, > Haisheng > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > Hi, > > > > I can volunteer for one of them, for example 1.26.0 > > > > Best regards, > > Ruben > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan < > >> hy...@apache.org> > >>> a > >> écrit > : > > > >> Hi, > >> > >> Would anyone be interested in being release manager for > >>> v1.26.0, > v1.27.0 > >> or v1.28.0? > >> We need 3 volunteers (must be PMC or committer) for these 3 > >> versions. > >> > >> Thanks, > >> Haisheng Yuan > >> > > > > >> > > > >>> > >> > >
Re: [DISCUSS] Release Managers
Release 2.0 is largely symbolic. We develop Calcite incrementally, so it’s more important that there are regular releases, and that they are backwards compatible (within reason), than what those releases are called. That said, a major release would be an opportunity to get rid of the cruft (deprecated APIs) that have built up over the years. We should do one at some point in 2021. Julian > On Feb 6, 2021, at 6:31 PM, Danny Chan wrote: > > Just curious, when does Calcit plan to release 2.0, there are so many small > versions now ~ Do we really need to be 1.3x.0 or 1.4x.0 version ? > > Andrei Sereda 于2021年2月5日周五 上午2:34写道： > >> I'm happy to help with 1.30 >> >> On Thu, Feb 4, 2021 at 1:27 PM Julian Hyde wrote: >> >>> Yes, I'll be release manager for 1.28. >>> >>> I think I promised to be a release manager a while ago. I forget which >>> release. Sorry about that. >>> >>> On Thu, Feb 4, 2021 at 1:09 AM Stamatis Zampetakis >>> wrote: That would be great Rui, thanks for volunteering. So far we have: 1.27 Stamatis 1.28 Julian ? 1.29 Rui It would be nice to also plan for 1.30 & 1.31 just to be a bit ahead of time. Are there other people willing to help? Best, Stamatis On Wed, Feb 3, 2021 at 12:32 AM Rui Wang wrote: > I can also help on releasing (haven't done one for Calcite). > > > -Rui > > On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde >> wrote: > >> I haven't been RM for a while. I'll do 1.27, then Stamatis can do >>> 1.28. >> >> On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis < >>> zabe...@gmail.com> >> wrote: >>> >>> Depending on the timing I can possibly get 1.27.0 or 1.28.0. >>> >>> Best, >>> Stamatis >>> >>> On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan > wrote: >>> Thanks for volunteering, Ruben! I think you can be the release > manager >> for 1.26.0. We still need 2 more volunteers for the next 2 versions. Thanks, Haisheng On 2020/07/25 15:24:43, Ruben Q L wrote: > Hi, > > I can volunteer for one of them, for example 1.26.0 > > Best regards, > Ruben > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan < >> hy...@apache.org> >>> a >> écrit : > >> Hi, >> >> Would anyone be interested in being release manager for >>> v1.26.0, v1.27.0 >> or v1.28.0? >> We need 3 volunteers (must be PMC or committer) for these 3 >> versions. >> >> Thanks, >> Haisheng Yuan >> > >> > >>> >>
Re: [DISCUSS] Release Managers
+1 with Danny Regards! Aron Tao Danny Chan 于2021年2月7日周日 上午10:31写道： > Just curious, when does Calcit plan to release 2.0, there are so many small > versions now ~ Do we really need to be 1.3x.0 or 1.4x.0 version ? > > Andrei Sereda 于2021年2月5日周五 上午2:34写道： > > > I'm happy to help with 1.30 > > > > On Thu, Feb 4, 2021 at 1:27 PM Julian Hyde wrote: > > > > > Yes, I'll be release manager for 1.28. > > > > > > I think I promised to be a release manager a while ago. I forget which > > > release. Sorry about that. > > > > > > On Thu, Feb 4, 2021 at 1:09 AM Stamatis Zampetakis > > > wrote: > > > > > > > > That would be great Rui, thanks for volunteering. So far we have: > > > > > > > > 1.27 Stamatis > > > > 1.28 Julian ? > > > > 1.29 Rui > > > > > > > > It would be nice to also plan for 1.30 & 1.31 just to be a bit ahead > of > > > > time. Are there other people willing to help? > > > > > > > > Best, > > > > Stamatis > > > > > > > > > > > > On Wed, Feb 3, 2021 at 12:32 AM Rui Wang > wrote: > > > > > > > > > I can also help on releasing (haven't done one for Calcite). > > > > > > > > > > > > > > > -Rui > > > > > > > > > > On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde > > wrote: > > > > > > > > > > > I haven't been RM for a while. I'll do 1.27, then Stamatis can do > > > 1.28. > > > > > > > > > > > > On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis < > > > zabe...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > > Depending on the timing I can possibly get 1.27.0 or 1.28.0. > > > > > > > > > > > > > > Best, > > > > > > > Stamatis > > > > > > > > > > > > > > On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan < > hy...@apache.org> > > > > > wrote: > > > > > > > > > > > > > > > Thanks for volunteering, Ruben! I think you can be the > release > > > > > manager > > > > > > for > > > > > > > > 1.26.0. > > > > > > > > > > > > > > > > We still need 2 more volunteers for the next 2 versions. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Haisheng > > > > > > > > > > > > > > > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > I can volunteer for one of them, for example 1.26.0 > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > Ruben > > > > > > > > > > > > > > > > > > > > > > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan < > > hy...@apache.org> > > > a > > > > > > écrit > > > > > > > > : > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > Would anyone be interested in being release manager for > > > v1.26.0, > > > > > > > > v1.27.0 > > > > > > > > > > or v1.28.0? > > > > > > > > > > We need 3 volunteers (must be PMC or committer) for > these 3 > > > > > > versions. > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > Haisheng Yuan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Release Managers
Just curious, when does Calcit plan to release 2.0, there are so many small versions now ~ Do we really need to be 1.3x.0 or 1.4x.0 version ? Andrei Sereda 于2021年2月5日周五 上午2:34写道： > I'm happy to help with 1.30 > > On Thu, Feb 4, 2021 at 1:27 PM Julian Hyde wrote: > > > Yes, I'll be release manager for 1.28. > > > > I think I promised to be a release manager a while ago. I forget which > > release. Sorry about that. > > > > On Thu, Feb 4, 2021 at 1:09 AM Stamatis Zampetakis > > wrote: > > > > > > That would be great Rui, thanks for volunteering. So far we have: > > > > > > 1.27 Stamatis > > > 1.28 Julian ? > > > 1.29 Rui > > > > > > It would be nice to also plan for 1.30 & 1.31 just to be a bit ahead of > > > time. Are there other people willing to help? > > > > > > Best, > > > Stamatis > > > > > > > > > On Wed, Feb 3, 2021 at 12:32 AM Rui Wang wrote: > > > > > > > I can also help on releasing (haven't done one for Calcite). > > > > > > > > > > > > -Rui > > > > > > > > On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde > wrote: > > > > > > > > > I haven't been RM for a while. I'll do 1.27, then Stamatis can do > > 1.28. > > > > > > > > > > On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis < > > zabe...@gmail.com> > > > > > wrote: > > > > > > > > > > > > Depending on the timing I can possibly get 1.27.0 or 1.28.0. > > > > > > > > > > > > Best, > > > > > > Stamatis > > > > > > > > > > > > On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan > > > > wrote: > > > > > > > > > > > > > Thanks for volunteering, Ruben! I think you can be the release > > > > manager > > > > > for > > > > > > > 1.26.0. > > > > > > > > > > > > > > We still need 2 more volunteers for the next 2 versions. > > > > > > > > > > > > > > Thanks, > > > > > > > Haisheng > > > > > > > > > > > > > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > I can volunteer for one of them, for example 1.26.0 > > > > > > > > > > > > > > > > Best regards, > > > > > > > > Ruben > > > > > > > > > > > > > > > > > > > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan < > hy...@apache.org> > > a > > > > > écrit > > > > > > > : > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > Would anyone be interested in being release manager for > > v1.26.0, > > > > > > > v1.27.0 > > > > > > > > > or v1.28.0? > > > > > > > > > We need 3 volunteers (must be PMC or committer) for these 3 > > > > > versions. > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > Haisheng Yuan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Release Managers
I'm happy to help with 1.30 On Thu, Feb 4, 2021 at 1:27 PM Julian Hyde wrote: > Yes, I'll be release manager for 1.28. > > I think I promised to be a release manager a while ago. I forget which > release. Sorry about that. > > On Thu, Feb 4, 2021 at 1:09 AM Stamatis Zampetakis > wrote: > > > > That would be great Rui, thanks for volunteering. So far we have: > > > > 1.27 Stamatis > > 1.28 Julian ? > > 1.29 Rui > > > > It would be nice to also plan for 1.30 & 1.31 just to be a bit ahead of > > time. Are there other people willing to help? > > > > Best, > > Stamatis > > > > > > On Wed, Feb 3, 2021 at 12:32 AM Rui Wang wrote: > > > > > I can also help on releasing (haven't done one for Calcite). > > > > > > > > > -Rui > > > > > > On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde wrote: > > > > > > > I haven't been RM for a while. I'll do 1.27, then Stamatis can do > 1.28. > > > > > > > > On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis < > zabe...@gmail.com> > > > > wrote: > > > > > > > > > > Depending on the timing I can possibly get 1.27.0 or 1.28.0. > > > > > > > > > > Best, > > > > > Stamatis > > > > > > > > > > On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan > > > wrote: > > > > > > > > > > > Thanks for volunteering, Ruben! I think you can be the release > > > manager > > > > for > > > > > > 1.26.0. > > > > > > > > > > > > We still need 2 more volunteers for the next 2 versions. > > > > > > > > > > > > Thanks, > > > > > > Haisheng > > > > > > > > > > > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > > > > > > Hi, > > > > > > > > > > > > > > I can volunteer for one of them, for example 1.26.0 > > > > > > > > > > > > > > Best regards, > > > > > > > Ruben > > > > > > > > > > > > > > > > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan > a > > > > écrit > > > > > > : > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > Would anyone be interested in being release manager for > v1.26.0, > > > > > > v1.27.0 > > > > > > > > or v1.28.0? > > > > > > > > We need 3 volunteers (must be PMC or committer) for these 3 > > > > versions. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Haisheng Yuan > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Release Managers
Yes, I'll be release manager for 1.28. I think I promised to be a release manager a while ago. I forget which release. Sorry about that. On Thu, Feb 4, 2021 at 1:09 AM Stamatis Zampetakis wrote: > > That would be great Rui, thanks for volunteering. So far we have: > > 1.27 Stamatis > 1.28 Julian ? > 1.29 Rui > > It would be nice to also plan for 1.30 & 1.31 just to be a bit ahead of > time. Are there other people willing to help? > > Best, > Stamatis > > > On Wed, Feb 3, 2021 at 12:32 AM Rui Wang wrote: > > > I can also help on releasing (haven't done one for Calcite). > > > > > > -Rui > > > > On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde wrote: > > > > > I haven't been RM for a while. I'll do 1.27, then Stamatis can do 1.28. > > > > > > On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis > > > wrote: > > > > > > > > Depending on the timing I can possibly get 1.27.0 or 1.28.0. > > > > > > > > Best, > > > > Stamatis > > > > > > > > On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan > > wrote: > > > > > > > > > Thanks for volunteering, Ruben! I think you can be the release > > manager > > > for > > > > > 1.26.0. > > > > > > > > > > We still need 2 more volunteers for the next 2 versions. > > > > > > > > > > Thanks, > > > > > Haisheng > > > > > > > > > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > > > > > Hi, > > > > > > > > > > > > I can volunteer for one of them, for example 1.26.0 > > > > > > > > > > > > Best regards, > > > > > > Ruben > > > > > > > > > > > > > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan a > > > écrit > > > > > : > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > Would anyone be interested in being release manager for v1.26.0, > > > > > v1.27.0 > > > > > > > or v1.28.0? > > > > > > > We need 3 volunteers (must be PMC or committer) for these 3 > > > versions. > > > > > > > > > > > > > > Thanks, > > > > > > > Haisheng Yuan > > > > > > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Release Managers
That would be great Rui, thanks for volunteering. So far we have: 1.27 Stamatis 1.28 Julian ? 1.29 Rui It would be nice to also plan for 1.30 & 1.31 just to be a bit ahead of time. Are there other people willing to help? Best, Stamatis On Wed, Feb 3, 2021 at 12:32 AM Rui Wang wrote: > I can also help on releasing (haven't done one for Calcite). > > > -Rui > > On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde wrote: > > > I haven't been RM for a while. I'll do 1.27, then Stamatis can do 1.28. > > > > On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis > > wrote: > > > > > > Depending on the timing I can possibly get 1.27.0 or 1.28.0. > > > > > > Best, > > > Stamatis > > > > > > On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan > wrote: > > > > > > > Thanks for volunteering, Ruben! I think you can be the release > manager > > for > > > > 1.26.0. > > > > > > > > We still need 2 more volunteers for the next 2 versions. > > > > > > > > Thanks, > > > > Haisheng > > > > > > > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > > > > Hi, > > > > > > > > > > I can volunteer for one of them, for example 1.26.0 > > > > > > > > > > Best regards, > > > > > Ruben > > > > > > > > > > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan a > > écrit > > > > : > > > > > > > > > > > Hi, > > > > > > > > > > > > Would anyone be interested in being release manager for v1.26.0, > > > > v1.27.0 > > > > > > or v1.28.0? > > > > > > We need 3 volunteers (must be PMC or committer) for these 3 > > versions. > > > > > > > > > > > > Thanks, > > > > > > Haisheng Yuan > > > > > > > > > > > > > > > > > >
Re: [DISCUSS] Release Managers
I can also help on releasing (haven't done one for Calcite). -Rui On Tue, Aug 18, 2020 at 2:32 PM Julian Hyde wrote: > I haven't been RM for a while. I'll do 1.27, then Stamatis can do 1.28. > > On Sun, Aug 16, 2020 at 1:57 AM Stamatis Zampetakis > wrote: > > > > Depending on the timing I can possibly get 1.27.0 or 1.28.0. > > > > Best, > > Stamatis > > > > On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan wrote: > > > > > Thanks for volunteering, Ruben! I think you can be the release manager > for > > > 1.26.0. > > > > > > We still need 2 more volunteers for the next 2 versions. > > > > > > Thanks, > > > Haisheng > > > > > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > > > Hi, > > > > > > > > I can volunteer for one of them, for example 1.26.0 > > > > > > > > Best regards, > > > > Ruben > > > > > > > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan a > écrit > > > : > > > > > > > > > Hi, > > > > > > > > > > Would anyone be interested in being release manager for v1.26.0, > > > v1.27.0 > > > > > or v1.28.0? > > > > > We need 3 volunteers (must be PMC or committer) for these 3 > versions. > > > > > > > > > > Thanks, > > > > > Haisheng Yuan > > > > > > > > > > > > >
Re: [DISCUSS] Release Managers
Depending on the timing I can possibly get 1.27.0 or 1.28.0. Best, Stamatis On Fri, Aug 14, 2020 at 2:58 AM Haisheng Yuan wrote: > Thanks for volunteering, Ruben! I think you can be the release manager for > 1.26.0. > > We still need 2 more volunteers for the next 2 versions. > > Thanks, > Haisheng > > On 2020/07/25 15:24:43, Ruben Q L wrote: > > Hi, > > > > I can volunteer for one of them, for example 1.26.0 > > > > Best regards, > > Ruben > > > > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan a écrit > : > > > > > Hi, > > > > > > Would anyone be interested in being release manager for v1.26.0, > v1.27.0 > > > or v1.28.0? > > > We need 3 volunteers (must be PMC or committer) for these 3 versions. > > > > > > Thanks, > > > Haisheng Yuan > > > > > >
Re: [DISCUSS] Release Managers
Thanks for volunteering, Ruben! I think you can be the release manager for 1.26.0. We still need 2 more volunteers for the next 2 versions. Thanks, Haisheng On 2020/07/25 15:24:43, Ruben Q L wrote: > Hi, > > I can volunteer for one of them, for example 1.26.0 > > Best regards, > Ruben > > > Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan a écrit : > > > Hi, > > > > Would anyone be interested in being release manager for v1.26.0, v1.27.0 > > or v1.28.0? > > We need 3 volunteers (must be PMC or committer) for these 3 versions. > > > > Thanks, > > Haisheng Yuan > > >
Re: [DISCUSS] Release Managers
Hi, I can volunteer for one of them, for example 1.26.0 Best regards, Ruben Le sam. 25 juil. 2020 à 15:23, Haisheng Yuan a écrit : > Hi, > > Would anyone be interested in being release manager for v1.26.0, v1.27.0 > or v1.28.0? > We need 3 volunteers (must be PMC or committer) for these 3 versions. > > Thanks, > Haisheng Yuan >
[DISCUSS] Release Managers
Hi, Would anyone be interested in being release manager for v1.26.0, v1.27.0 or v1.28.0? We need 3 volunteers (must be PMC or committer) for these 3 versions. Thanks, Haisheng Yuan
Re: Release managers
I was mistaken in saying that only a PMC can sign a release. Any committer may be a release manager, and sign the release. In http://www.apache.org/dev/release-publishing.html#release_manager: "Any committer may serve as the manager of a release" Julian On Fri, Dec 6, 2019 at 9:41 AM Vladimir Sitnikov wrote: > > Enrico>AFAIK in all of the apache projects I am contributing to as > committer every > Enrico>committer can sign the artifacts and be release manager > > There existed META effort (which was hosted at > https://checker.apache.org/#META-files), however, it looks like > checker.apache.org was dropped recently by infra, so the future is not > clear. > META files described who must sign what so the release to be considered to > be an official one. > For instance, JMeter still has a META file that specifies who must sign the > releases: https://dist.apache.org/repos/dist/release/jmeter/META , > and there's a root file that specifies who signs per-project META files: > https://dist.apache.org/repos/dist/release/META/ROOT > > The current META/ROOT contains > > # pmc calcite [chair] francischuang > key bbe44e923a970ab7 signs calcite/META > > Vladimir
Re: Release managers
Enrico>AFAIK in all of the apache projects I am contributing to as committer every Enrico>committer can sign the artifacts and be release manager There existed META effort (which was hosted at https://checker.apache.org/#META-files), however, it looks like checker.apache.org was dropped recently by infra, so the future is not clear. META files described who must sign what so the release to be considered to be an official one. For instance, JMeter still has a META file that specifies who must sign the releases: https://dist.apache.org/repos/dist/release/jmeter/META , and there's a root file that specifies who signs per-project META files: https://dist.apache.org/repos/dist/release/META/ROOT The current META/ROOT contains # pmc calcite [chair] francischuang key bbe44e923a970ab7 signs calcite/META Vladimir
Re: Release managers
Hi, AFAIK in all of the apache projects I am contributing to as committer every committer can sign the artifacts and be release manager, the PMC has just to VOTE or do some Apache reporter stuff or other bureaucratic stuff. Is there any particular rule here in Calcite project? If it is not the case I suggest to open the ability of signing artifacts to any committer that has a GPG key valid and part of the Apache Web of Trust Just my two sents Enrico Il mar 3 dic 2019, 02:11 Chunwei Lei ha scritto: > It's great to know that committers can be release manager. > I volunteer to be the release manager if there is a chance. > > BTW, If Julian doesn't mind, I would like to take 1.24 ~~ > > > Best, > Chunwei > > > On Tue, Dec 3, 2019 at 5:43 AM Francis Chuang > wrote: > > > Just a quick note regarding the move to Gradle as the build tool for > > release. Thanks to Vladimir, the release process is almost entirely > > automated and the rc can be built and automatically uploaded to ASF's > > servers for voting using just one command: ./gradlew prepareVote -Prc=0 > > -Pasf This builds the artifacts, signs them and uploads them to > > dist.apache.org. > > > > If the RM is a committer, then I think they should do a dry-run to test > > the build, but not upload it. The asflike-release-environment[1] should > > be used to try uploading the release to a test environment: ./gradlew > > prepareVote -Prc=0. > > > > Once everything looks good, a PMC member should build and upload the > > signed release using ./gradlew prepareVote -Prc=0 -Pasf and forward the > > vote email to the RM. > > > > In the past, maven only built the artifacts and left the uploading of > > the files as a manual exercise to the RM, so the process has changed > > slightly this time. > > > > Francis > > > > [1] https://github.com/vlsi/asflike-release-environment > > > > On 3/12/2019 6:03 am, Julian Hyde wrote: > > > I volunteer to do 1.24. > > > > > > There’s one part of the release process that only a PMC member can do - > > namely, to sign the artifacts. But that’s only a small part of the > process, > > and you can easily get a PMC member to do it for you. A much larger part > of > > the process is the herding of cats (committers, bugs, pull requests, > > release notes). So, yes, a committer can definitely be a release manager. > > > > > > How does the PMC decide which committers to promote to PMC members? We > > are looking for people who help out around the project, going above and > > beyond the basic needs of each task to make the project a better place. > If > > you are a committer, helping with the release process is a good way to > earn > > merit. > > > > > > Julian > > > > > > > > >> On Dec 2, 2019, at 10:48 AM, Stamatis Zampetakis > > wrote: > > >> > > >> Many thanks Haisheng and Danny for stepping up! I added you to the > list. > > >> There are two spots left, if nobody else comes up I will take one of > > them! > > >> > > >> Release Target date Release manager > > >> === === === > > >> 1.192019-03Kevin > > >> 1.202019-06Michael > > >> 1.212019-09Stamatis > > >> === === === > > >> 1.222019-12Andrei > > >> 1.232020-02Haisheng > > >> 1.242020-04Julian > > >> 1.252020-06Danny > > >> 1.262020-08 > > >> > > >> > > >> > > >> On Sat, Nov 30, 2019 at 9:52 AM Danny Chan > > wrote: > > >> > > >>> BTW, > > >>> I can volunteer to be the release manager for v1.25 or v1.26. > > >>> > > >>> Best, > > >>> Danny Chan > > >>> 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： > > > > I can volunteer to be the release manager for v1.23 or v1.24. > > >>> > > > > > >
Re: Release managers
Many thanks, Julian. +1 for Avatica release-train. Best, Chunwei On Thu, Dec 5, 2019 at 6:06 AM Julian Hyde wrote: > Sure, take 1.24. > > By the way, if people are eager to be release managers, we might need some > for Avatica release-train. > > > > > On Dec 2, 2019, at 5:11 PM, Chunwei Lei wrote: > > > > It's great to know that committers can be release manager. > > I volunteer to be the release manager if there is a chance. > > > > BTW, If Julian doesn't mind, I would like to take 1.24 ~~ > > > > > > Best, > > Chunwei > > > > > > On Tue, Dec 3, 2019 at 5:43 AM Francis Chuang > > wrote: > > > >> Just a quick note regarding the move to Gradle as the build tool for > >> release. Thanks to Vladimir, the release process is almost entirely > >> automated and the rc can be built and automatically uploaded to ASF's > >> servers for voting using just one command: ./gradlew prepareVote -Prc=0 > >> -Pasf This builds the artifacts, signs them and uploads them to > >> dist.apache.org. > >> > >> If the RM is a committer, then I think they should do a dry-run to test > >> the build, but not upload it. The asflike-release-environment[1] should > >> be used to try uploading the release to a test environment: ./gradlew > >> prepareVote -Prc=0. > >> > >> Once everything looks good, a PMC member should build and upload the > >> signed release using ./gradlew prepareVote -Prc=0 -Pasf and forward the > >> vote email to the RM. > >> > >> In the past, maven only built the artifacts and left the uploading of > >> the files as a manual exercise to the RM, so the process has changed > >> slightly this time. > >> > >> Francis > >> > >> [1] https://github.com/vlsi/asflike-release-environment > >> > >> On 3/12/2019 6:03 am, Julian Hyde wrote: > >>> I volunteer to do 1.24. > >>> > >>> There’s one part of the release process that only a PMC member can do - > >> namely, to sign the artifacts. But that’s only a small part of the > process, > >> and you can easily get a PMC member to do it for you. A much larger > part of > >> the process is the herding of cats (committers, bugs, pull requests, > >> release notes). So, yes, a committer can definitely be a release > manager. > >>> > >>> How does the PMC decide which committers to promote to PMC members? We > >> are looking for people who help out around the project, going above and > >> beyond the basic needs of each task to make the project a better > place. If > >> you are a committer, helping with the release process is a good way to > earn > >> merit. > >>> > >>> Julian > >>> > >>> > >>>> On Dec 2, 2019, at 10:48 AM, Stamatis Zampetakis > >> wrote: > >>>> > >>>> Many thanks Haisheng and Danny for stepping up! I added you to the > list. > >>>> There are two spots left, if nobody else comes up I will take one of > >> them! > >>>> > >>>> Release Target date Release manager > >>>> === === === > >>>> 1.192019-03Kevin > >>>> 1.202019-06Michael > >>>> 1.212019-09Stamatis > >>>> === === === > >>>> 1.222019-12Andrei > >>>> 1.232020-02Haisheng > >>>> 1.242020-04Julian > >>>> 1.252020-06Danny > >>>> 1.262020-08 > >>>> > >>>> > >>>> > >>>> On Sat, Nov 30, 2019 at 9:52 AM Danny Chan > >> wrote: > >>>> > >>>>> BTW, > >>>>> I can volunteer to be the release manager for v1.25 or v1.26. > >>>>> > >>>>> Best, > >>>>> Danny Chan > >>>>> 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： > >>>>>> > >>>>>> I can volunteer to be the release manager for v1.23 or v1.24. > >>>>> > >>> > >> > >
Re: Release managers
Sure, take 1.24. By the way, if people are eager to be release managers, we might need some for Avatica release-train. > On Dec 2, 2019, at 5:11 PM, Chunwei Lei wrote: > > It's great to know that committers can be release manager. > I volunteer to be the release manager if there is a chance. > > BTW, If Julian doesn't mind, I would like to take 1.24 ~~ > > > Best, > Chunwei > > > On Tue, Dec 3, 2019 at 5:43 AM Francis Chuang > wrote: > >> Just a quick note regarding the move to Gradle as the build tool for >> release. Thanks to Vladimir, the release process is almost entirely >> automated and the rc can be built and automatically uploaded to ASF's >> servers for voting using just one command: ./gradlew prepareVote -Prc=0 >> -Pasf This builds the artifacts, signs them and uploads them to >> dist.apache.org. >> >> If the RM is a committer, then I think they should do a dry-run to test >> the build, but not upload it. The asflike-release-environment[1] should >> be used to try uploading the release to a test environment: ./gradlew >> prepareVote -Prc=0. >> >> Once everything looks good, a PMC member should build and upload the >> signed release using ./gradlew prepareVote -Prc=0 -Pasf and forward the >> vote email to the RM. >> >> In the past, maven only built the artifacts and left the uploading of >> the files as a manual exercise to the RM, so the process has changed >> slightly this time. >> >> Francis >> >> [1] https://github.com/vlsi/asflike-release-environment >> >> On 3/12/2019 6:03 am, Julian Hyde wrote: >>> I volunteer to do 1.24. >>> >>> There’s one part of the release process that only a PMC member can do - >> namely, to sign the artifacts. But that’s only a small part of the process, >> and you can easily get a PMC member to do it for you. A much larger part of >> the process is the herding of cats (committers, bugs, pull requests, >> release notes). So, yes, a committer can definitely be a release manager. >>> >>> How does the PMC decide which committers to promote to PMC members? We >> are looking for people who help out around the project, going above and >> beyond the basic needs of each task to make the project a better place. If >> you are a committer, helping with the release process is a good way to earn >> merit. >>> >>> Julian >>> >>> >>>> On Dec 2, 2019, at 10:48 AM, Stamatis Zampetakis >> wrote: >>>> >>>> Many thanks Haisheng and Danny for stepping up! I added you to the list. >>>> There are two spots left, if nobody else comes up I will take one of >> them! >>>> >>>> Release Target date Release manager >>>> === === === >>>> 1.192019-03Kevin >>>> 1.202019-06Michael >>>> 1.212019-09Stamatis >>>> === === === >>>> 1.222019-12Andrei >>>> 1.232020-02Haisheng >>>> 1.242020-04Julian >>>> 1.252020-06Danny >>>> 1.262020-08 >>>> >>>> >>>> >>>> On Sat, Nov 30, 2019 at 9:52 AM Danny Chan >> wrote: >>>> >>>>> BTW, >>>>> I can volunteer to be the release manager for v1.25 or v1.26. >>>>> >>>>> Best, >>>>> Danny Chan >>>>> 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： >>>>>> >>>>>> I can volunteer to be the release manager for v1.23 or v1.24. >>>>> >>> >>
Re: Release managers
It's great to know that committers can be release manager. I volunteer to be the release manager if there is a chance. BTW, If Julian doesn't mind, I would like to take 1.24 ~~ Best, Chunwei On Tue, Dec 3, 2019 at 5:43 AM Francis Chuang wrote: > Just a quick note regarding the move to Gradle as the build tool for > release. Thanks to Vladimir, the release process is almost entirely > automated and the rc can be built and automatically uploaded to ASF's > servers for voting using just one command: ./gradlew prepareVote -Prc=0 > -Pasf This builds the artifacts, signs them and uploads them to > dist.apache.org. > > If the RM is a committer, then I think they should do a dry-run to test > the build, but not upload it. The asflike-release-environment[1] should > be used to try uploading the release to a test environment: ./gradlew > prepareVote -Prc=0. > > Once everything looks good, a PMC member should build and upload the > signed release using ./gradlew prepareVote -Prc=0 -Pasf and forward the > vote email to the RM. > > In the past, maven only built the artifacts and left the uploading of > the files as a manual exercise to the RM, so the process has changed > slightly this time. > > Francis > > [1] https://github.com/vlsi/asflike-release-environment > > On 3/12/2019 6:03 am, Julian Hyde wrote: > > I volunteer to do 1.24. > > > > There’s one part of the release process that only a PMC member can do - > namely, to sign the artifacts. But that’s only a small part of the process, > and you can easily get a PMC member to do it for you. A much larger part of > the process is the herding of cats (committers, bugs, pull requests, > release notes). So, yes, a committer can definitely be a release manager. > > > > How does the PMC decide which committers to promote to PMC members? We > are looking for people who help out around the project, going above and > beyond the basic needs of each task to make the project a better place. If > you are a committer, helping with the release process is a good way to earn > merit. > > > > Julian > > > > > >> On Dec 2, 2019, at 10:48 AM, Stamatis Zampetakis > wrote: > >> > >> Many thanks Haisheng and Danny for stepping up! I added you to the list. > >> There are two spots left, if nobody else comes up I will take one of > them! > >> > >> Release Target date Release manager > >> === === === > >> 1.192019-03Kevin > >> 1.202019-06Michael > >> 1.212019-09Stamatis > >> === === === > >> 1.222019-12Andrei > >> 1.232020-02Haisheng > >> 1.242020-04Julian > >> 1.252020-06Danny > >> 1.262020-08 > >> > >> > >> > >> On Sat, Nov 30, 2019 at 9:52 AM Danny Chan > wrote: > >> > >>> BTW, > >>> I can volunteer to be the release manager for v1.25 or v1.26. > >>> > >>> Best, > >>> Danny Chan > >>> 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： > > I can volunteer to be the release manager for v1.23 or v1.24. > >>> > > >
Re: Release managers
Just a quick note regarding the move to Gradle as the build tool for release. Thanks to Vladimir, the release process is almost entirely automated and the rc can be built and automatically uploaded to ASF's servers for voting using just one command: ./gradlew prepareVote -Prc=0 -Pasf This builds the artifacts, signs them and uploads them to dist.apache.org. If the RM is a committer, then I think they should do a dry-run to test the build, but not upload it. The asflike-release-environment[1] should be used to try uploading the release to a test environment: ./gradlew prepareVote -Prc=0. Once everything looks good, a PMC member should build and upload the signed release using ./gradlew prepareVote -Prc=0 -Pasf and forward the vote email to the RM. In the past, maven only built the artifacts and left the uploading of the files as a manual exercise to the RM, so the process has changed slightly this time. Francis [1] https://github.com/vlsi/asflike-release-environment On 3/12/2019 6:03 am, Julian Hyde wrote: I volunteer to do 1.24. There’s one part of the release process that only a PMC member can do - namely, to sign the artifacts. But that’s only a small part of the process, and you can easily get a PMC member to do it for you. A much larger part of the process is the herding of cats (committers, bugs, pull requests, release notes). So, yes, a committer can definitely be a release manager. How does the PMC decide which committers to promote to PMC members? We are looking for people who help out around the project, going above and beyond the basic needs of each task to make the project a better place. If you are a committer, helping with the release process is a good way to earn merit. Julian On Dec 2, 2019, at 10:48 AM, Stamatis Zampetakis wrote: Many thanks Haisheng and Danny for stepping up! I added you to the list. There are two spots left, if nobody else comes up I will take one of them! Release Target date Release manager === === === 1.192019-03Kevin 1.202019-06Michael 1.212019-09Stamatis === === === 1.222019-12Andrei 1.232020-02Haisheng 1.242020-04Julian 1.252020-06Danny 1.262020-08 On Sat, Nov 30, 2019 at 9:52 AM Danny Chan wrote: BTW, I can volunteer to be the release manager for v1.25 or v1.26. Best, Danny Chan 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： I can volunteer to be the release manager for v1.23 or v1.24.
Re: Release managers
I volunteer to do 1.24. There’s one part of the release process that only a PMC member can do - namely, to sign the artifacts. But that’s only a small part of the process, and you can easily get a PMC member to do it for you. A much larger part of the process is the herding of cats (committers, bugs, pull requests, release notes). So, yes, a committer can definitely be a release manager. How does the PMC decide which committers to promote to PMC members? We are looking for people who help out around the project, going above and beyond the basic needs of each task to make the project a better place. If you are a committer, helping with the release process is a good way to earn merit. Julian > On Dec 2, 2019, at 10:48 AM, Stamatis Zampetakis wrote: > > Many thanks Haisheng and Danny for stepping up! I added you to the list. > There are two spots left, if nobody else comes up I will take one of them! > > Release Target date Release manager > === === === > 1.192019-03Kevin > 1.202019-06Michael > 1.212019-09Stamatis > === === === > 1.222019-12Andrei > 1.232020-02Haisheng > 1.242020-04Julian > 1.252020-06Danny > 1.262020-08 > > > > On Sat, Nov 30, 2019 at 9:52 AM Danny Chan wrote: > >> BTW, >> I can volunteer to be the release manager for v1.25 or v1.26. >> >> Best, >> Danny Chan >> 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： >>> >>> I can volunteer to be the release manager for v1.23 or v1.24. >>
Re: Release managers
Actually, if Danny doesn't mind, I'll take 1.25 and he can take 1.26. -- Michael Mior mm...@apache.org Le lun. 2 déc. 2019 à 13:48, Stamatis Zampetakis a écrit : > > Many thanks Haisheng and Danny for stepping up! I added you to the list. > There are two spots left, if nobody else comes up I will take one of them! > > Release Target date Release manager > === === === > 1.192019-03Kevin > 1.202019-06Michael > 1.212019-09Stamatis > === === === > 1.222019-12Andrei > 1.232020-02Haisheng > 1.242020-04 > 1.252020-06Danny > 1.262020-08 > > > > On Sat, Nov 30, 2019 at 9:52 AM Danny Chan wrote: > > > BTW, > > I can volunteer to be the release manager for v1.25 or v1.26. > > > > Best, > > Danny Chan > > 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： > > > > > > I can volunteer to be the release manager for v1.23 or v1.24. > >
Re: Release managers
Many thanks Haisheng and Danny for stepping up! I added you to the list. There are two spots left, if nobody else comes up I will take one of them! Release Target date Release manager === === === 1.192019-03Kevin 1.202019-06Michael 1.212019-09Stamatis === === === 1.222019-12Andrei 1.232020-02Haisheng 1.242020-04 1.252020-06Danny 1.262020-08 On Sat, Nov 30, 2019 at 9:52 AM Danny Chan wrote: > BTW, > I can volunteer to be the release manager for v1.25 or v1.26. > > Best, > Danny Chan > 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： > > > > I can volunteer to be the release manager for v1.23 or v1.24. >
Re: Release managers
BTW, I can volunteer to be the release manager for v1.25 or v1.26. Best, Danny Chan 在 2019年11月30日 +0800 PM2:13，dev@calcite.apache.org，写道： > > I can volunteer to be the release manager for v1.23 or v1.24.
Re: Release managers
Oh, I always thought that only PMC can be a release manager, I’m glad that now all the committers can do that ~ I believe that the release work would not be much burden in the future :) Best, Danny Chan 在 2019年11月30日 +0800 AM12:53，Stamatis Zampetakis ，写道： > Hi all, > > The pre-selection of release managers [1] has worked very well so far. It > would be great if we could have some volunteers for the next releases. > > Release Target date Release manager > === === === > 1.19 2019-03 Kevin > 1.20 2019-06 Michael > 1.21 2019-09 Stamatis > === === === > 1.22 2019-12 Andrei > 1.23 2020-02 > 1.24 2020-04 > 1.25 2020-06 > 1.26 2020-08 > > As a reminder the RM does not have to be a PMC member (commitership is > necessary). > > Best, > Stamatis > > [1] > https://lists.apache.org/thread.html/c6fba3f6585139ba6919baf71835d32eeea8ca187621aa5c06a26f8c@%3Cdev.calcite.apache.org%3E
Re: Release managers
Hi Stamatis, I can volunteer to be the release manager for v1.23 or v1.24. - Haisheng -- 发件人：Stamatis Zampetakis 日 期：2019年11月30日 00:53:34 收件人： 主 题：Release managers Hi all, The pre-selection of release managers [1] has worked very well so far. It would be great if we could have some volunteers for the next releases. Release Target date Release manager === === === 1.192019-03Kevin 1.202019-06Michael 1.212019-09Stamatis === === === 1.222019-12Andrei 1.232020-02 1.242020-04 1.252020-06 1.262020-08 As a reminder the RM does not have to be a PMC member (commitership is necessary). Best, Stamatis [1] https://lists.apache.org/thread.html/c6fba3f6585139ba6919baf71835d32eeea8ca187621aa5c06a26f8c@%3Cdev.calcite.apache.org%3E
Re: Release managers
Hi Kevin, this should make things easier definitely and speed up the process. Julian Am 11.02.19, 15:39 schrieb "Kevin Risden" : I can volunteer to do the 1.19 2019-02 release. We are getting to midway through February :) Kevin Risden On Thu, Feb 7, 2019 at 3:23 AM Julian Feinauer wrote: > Hey all, > > I don't know if this is unusual or undoable due to permission issues as > I'm no commiter. > But I'd like to offer my duties as RM. > I am not that familiar with Calcite releases but just finished my first > official release for an Apache Projekt with PLC4X. > > Best > Julian > > > Am 06.02.19, 21:00 schrieb "Julian Hyde" : > > Any volunteers for 1.19? > > We now have > > Release Target date Release manager > === === === > 1.192019-02 > 1.202019-04Michael Mior > 1.212019-06Stamatis > 1.222019-08 Andrei > 1.232019-10 > > > On Feb 4, 2019, at 10:17 AM, Michael Mior wrote: > > > > Great idea. I was intending to volunteer as RM last time, but with > the > > time pressure, I didn't respond soon enough. I'm happy to take the > > April release (1.20). > > > > -- > > Michael Mior > > mm...@apache.org > > > > Le jeu. 31 janv. 2019 à 18:54, Andrei Sereda a > écrit : > >> > >> Release Target date Release manager > >> === === === > >> 1.192019-02 > >> 1.202019-04 > >> 1.212019-06Stamatis > >> 1.222019-08 Andrei > >> 1.232019-10 > >> > >> On Thu, Jan 31, 2019 at 6:14 PM Stamatis Zampetakis < > zabe...@gmail.com> > >> wrote: > >> > >>> Release Target date Release manager > >>> === === === > >>> 1.192019-02 > >>> 1.202019-04 > >>> 1.212019-06Stamatis > >>> 1.222019-08 > >>> 1.232019-10 > >>> > >>> Στις Πέμ, 31 Ιαν 2019 στις 7:46 μ.μ., ο/η Julian Hyde < > jh...@apache.org> > >>> έγραψε: > >>> > >>>> Calcite needs to make regular releases, and we have established a > cadence > >>>> of every 2 - 3 months that everyone seems to like. But to keep > that > >>>> running, each release needs a release manager, and finding a > release > >>>> manager always seems to be a chore. > >>>> > >>>> I wonder if we have trouble recruiting release managers because > we only > >>>> ask for one at a time. How about we get volunteers for the next 5 > >>> releases? > >>>> Then everyone will be seen to be doing their fair share. > >>>> > >>>> Release Target date Release manager > >>>> === === === > >>>> 1.192019-02 > >>>> 1.202019-04 > >>>> 1.212019-06 > >>>> 1.222019-08 > >>>> 1.232019-10 > >>>> > >>>> I propose that frequent committers (anyone who had 2 or more > fixes in > >>> 1.18 > >>>> and 1 or 2 fixes in 1.16 or 1.17) should all step up and be > release > >>> manager > >>>> for one of the releases this year. > >>>> > >>>> Julian > >>>> > >>>> > >>> > > > >
Re: Release managers
I can volunteer to do the 1.19 2019-02 release. We are getting to midway through February :) Kevin Risden On Thu, Feb 7, 2019 at 3:23 AM Julian Feinauer wrote: > Hey all, > > I don't know if this is unusual or undoable due to permission issues as > I'm no commiter. > But I'd like to offer my duties as RM. > I am not that familiar with Calcite releases but just finished my first > official release for an Apache Projekt with PLC4X. > > Best > Julian > > > Am 06.02.19, 21:00 schrieb "Julian Hyde" : > > Any volunteers for 1.19? > > We now have > > Release Target date Release manager > === === === > 1.192019-02 > 1.202019-04Michael Mior > 1.212019-06Stamatis > 1.222019-08 Andrei > 1.232019-10 > > > On Feb 4, 2019, at 10:17 AM, Michael Mior wrote: > > > > Great idea. I was intending to volunteer as RM last time, but with > the > > time pressure, I didn't respond soon enough. I'm happy to take the > > April release (1.20). > > > > -- > > Michael Mior > > mm...@apache.org > > > > Le jeu. 31 janv. 2019 à 18:54, Andrei Sereda a > écrit : > >> > >> Release Target date Release manager > >> === === === > >> 1.192019-02 > >> 1.202019-04 > >> 1.212019-06Stamatis > >> 1.222019-08 Andrei > >> 1.232019-10 > >> > >> On Thu, Jan 31, 2019 at 6:14 PM Stamatis Zampetakis < > zabe...@gmail.com> > >> wrote: > >> > >>> Release Target date Release manager > >>> === === === > >>> 1.192019-02 > >>> 1.202019-04 > >>> 1.212019-06Stamatis > >>> 1.222019-08 > >>> 1.232019-10 > >>> > >>> Στις Πέμ, 31 Ιαν 2019 στις 7:46 μ.μ., ο/η Julian Hyde < > jh...@apache.org> > >>> έγραψε: > >>> > >>>> Calcite needs to make regular releases, and we have established a > cadence > >>>> of every 2 - 3 months that everyone seems to like. But to keep > that > >>>> running, each release needs a release manager, and finding a > release > >>>> manager always seems to be a chore. > >>>> > >>>> I wonder if we have trouble recruiting release managers because > we only > >>>> ask for one at a time. How about we get volunteers for the next 5 > >>> releases? > >>>> Then everyone will be seen to be doing their fair share. > >>>> > >>>> Release Target date Release manager > >>>> === === === > >>>> 1.192019-02 > >>>> 1.202019-04 > >>>> 1.212019-06 > >>>> 1.222019-08 > >>>> 1.232019-10 > >>>> > >>>> I propose that frequent committers (anyone who had 2 or more > fixes in > >>> 1.18 > >>>> and 1 or 2 fixes in 1.16 or 1.17) should all step up and be > release > >>> manager > >>>> for one of the releases this year. > >>>> > >>>> Julian > >>>> > >>>> > >>> > > > >
Re: Release managers
Hey all, I don't know if this is unusual or undoable due to permission issues as I'm no commiter. But I'd like to offer my duties as RM. I am not that familiar with Calcite releases but just finished my first official release for an Apache Projekt with PLC4X. Best Julian Am 06.02.19, 21:00 schrieb "Julian Hyde" : Any volunteers for 1.19? We now have Release Target date Release manager === === === 1.192019-02 1.202019-04Michael Mior 1.212019-06Stamatis 1.222019-08 Andrei 1.232019-10 > On Feb 4, 2019, at 10:17 AM, Michael Mior wrote: > > Great idea. I was intending to volunteer as RM last time, but with the > time pressure, I didn't respond soon enough. I'm happy to take the > April release (1.20). > > -- > Michael Mior > mm...@apache.org > > Le jeu. 31 janv. 2019 à 18:54, Andrei Sereda a écrit : >> >> Release Target date Release manager >> === === === >> 1.192019-02 >> 1.202019-04 >> 1.212019-06Stamatis >> 1.222019-08 Andrei >> 1.232019-10 >> >> On Thu, Jan 31, 2019 at 6:14 PM Stamatis Zampetakis >> wrote: >> >>> Release Target date Release manager >>> === === === >>> 1.192019-02 >>> 1.202019-04 >>> 1.212019-06Stamatis >>> 1.222019-08 >>> 1.232019-10 >>> >>> Στις Πέμ, 31 Ιαν 2019 στις 7:46 μ.μ., ο/η Julian Hyde >>> έγραψε: >>> >>>> Calcite needs to make regular releases, and we have established a cadence >>>> of every 2 - 3 months that everyone seems to like. But to keep that >>>> running, each release needs a release manager, and finding a release >>>> manager always seems to be a chore. >>>> >>>> I wonder if we have trouble recruiting release managers because we only >>>> ask for one at a time. How about we get volunteers for the next 5 >>> releases? >>>> Then everyone will be seen to be doing their fair share. >>>> >>>> Release Target date Release manager >>>> === === === >>>> 1.192019-02 >>>> 1.202019-04 >>>> 1.212019-06 >>>> 1.222019-08 >>>> 1.232019-10 >>>> >>>> I propose that frequent committers (anyone who had 2 or more fixes in >>> 1.18 >>>> and 1 or 2 fixes in 1.16 or 1.17) should all step up and be release >>> manager >>>> for one of the releases this year. >>>> >>>> Julian >>>> >>>> >>>
Re: Release managers
Any volunteers for 1.19? We now have Release Target date Release manager === === === 1.192019-02 1.202019-04Michael Mior 1.212019-06Stamatis 1.222019-08 Andrei 1.232019-10 > On Feb 4, 2019, at 10:17 AM, Michael Mior wrote: > > Great idea. I was intending to volunteer as RM last time, but with the > time pressure, I didn't respond soon enough. I'm happy to take the > April release (1.20). > > -- > Michael Mior > mm...@apache.org > > Le jeu. 31 janv. 2019 à 18:54, Andrei Sereda a écrit : >> >> Release Target date Release manager >> === === === >> 1.192019-02 >> 1.202019-04 >> 1.212019-06Stamatis >> 1.222019-08 Andrei >> 1.232019-10 >> >> On Thu, Jan 31, 2019 at 6:14 PM Stamatis Zampetakis >> wrote: >> >>> Release Target date Release manager >>> === === === >>> 1.192019-02 >>> 1.202019-04 >>> 1.212019-06Stamatis >>> 1.222019-08 >>> 1.232019-10 >>> >>> Στις Πέμ, 31 Ιαν 2019 στις 7:46 μ.μ., ο/η Julian Hyde >>> έγραψε: >>> >>>> Calcite needs to make regular releases, and we have established a cadence >>>> of every 2 - 3 months that everyone seems to like. But to keep that >>>> running, each release needs a release manager, and finding a release >>>> manager always seems to be a chore. >>>> >>>> I wonder if we have trouble recruiting release managers because we only >>>> ask for one at a time. How about we get volunteers for the next 5 >>> releases? >>>> Then everyone will be seen to be doing their fair share. >>>> >>>> Release Target date Release manager >>>> === === === >>>> 1.192019-02 >>>> 1.202019-04 >>>> 1.212019-06 >>>> 1.222019-08 >>>> 1.232019-10 >>>> >>>> I propose that frequent committers (anyone who had 2 or more fixes in >>> 1.18 >>>> and 1 or 2 fixes in 1.16 or 1.17) should all step up and be release >>> manager >>>> for one of the releases this year. >>>> >>>> Julian >>>> >>>> >>>
Re: Release managers
Great idea. I was intending to volunteer as RM last time, but with the time pressure, I didn't respond soon enough. I'm happy to take the April release (1.20). -- Michael Mior mm...@apache.org Le jeu. 31 janv. 2019 à 18:54, Andrei Sereda a écrit : > > Release Target date Release manager > === === === > 1.192019-02 > 1.202019-04 > 1.212019-06Stamatis > 1.222019-08 Andrei > 1.232019-10 > > On Thu, Jan 31, 2019 at 6:14 PM Stamatis Zampetakis > wrote: > > > Release Target date Release manager > > === === === > > 1.192019-02 > > 1.202019-04 > > 1.212019-06Stamatis > > 1.222019-08 > > 1.232019-10 > > > > Στις Πέμ, 31 Ιαν 2019 στις 7:46 μ.μ., ο/η Julian Hyde > > έγραψε: > > > > > Calcite needs to make regular releases, and we have established a cadence > > > of every 2 - 3 months that everyone seems to like. But to keep that > > > running, each release needs a release manager, and finding a release > > > manager always seems to be a chore. > > > > > > I wonder if we have trouble recruiting release managers because we only > > > ask for one at a time. How about we get volunteers for the next 5 > > releases? > > > Then everyone will be seen to be doing their fair share. > > > > > > Release Target date Release manager > > > === === === > > > 1.192019-02 > > > 1.202019-04 > > > 1.212019-06 > > > 1.222019-08 > > > 1.232019-10 > > > > > > I propose that frequent committers (anyone who had 2 or more fixes in > > 1.18 > > > and 1 or 2 fixes in 1.16 or 1.17) should all step up and be release > > manager > > > for one of the releases this year. > > > > > > Julian > > > > > > > >
Re: Release managers
Release Target date Release manager === === === 1.192019-02 1.202019-04 1.212019-06Stamatis 1.222019-08 Andrei 1.232019-10 On Thu, Jan 31, 2019 at 6:14 PM Stamatis Zampetakis wrote: > Release Target date Release manager > === === === > 1.192019-02 > 1.202019-04 > 1.212019-06Stamatis > 1.222019-08 > 1.232019-10 > > Στις Πέμ, 31 Ιαν 2019 στις 7:46 μ.μ., ο/η Julian Hyde > έγραψε: > > > Calcite needs to make regular releases, and we have established a cadence > > of every 2 - 3 months that everyone seems to like. But to keep that > > running, each release needs a release manager, and finding a release > > manager always seems to be a chore. > > > > I wonder if we have trouble recruiting release managers because we only > > ask for one at a time. How about we get volunteers for the next 5 > releases? > > Then everyone will be seen to be doing their fair share. > > > > Release Target date Release manager > > === === === > > 1.192019-02 > > 1.202019-04 > > 1.212019-06 > > 1.222019-08 > > 1.232019-10 > > > > I propose that frequent committers (anyone who had 2 or more fixes in > 1.18 > > and 1 or 2 fixes in 1.16 or 1.17) should all step up and be release > manager > > for one of the releases this year. > > > > Julian > > > > >
Re: Release managers
Release Target date Release manager === === === 1.192019-02 1.202019-04 1.212019-06Stamatis 1.222019-08 1.232019-10 Στις Πέμ, 31 Ιαν 2019 στις 7:46 μ.μ., ο/η Julian Hyde έγραψε: > Calcite needs to make regular releases, and we have established a cadence > of every 2 - 3 months that everyone seems to like. But to keep that > running, each release needs a release manager, and finding a release > manager always seems to be a chore. > > I wonder if we have trouble recruiting release managers because we only > ask for one at a time. How about we get volunteers for the next 5 releases? > Then everyone will be seen to be doing their fair share. > > Release Target date Release manager > === === === > 1.192019-02 > 1.202019-04 > 1.212019-06 > 1.222019-08 > 1.232019-10 > > I propose that frequent committers (anyone who had 2 or more fixes in 1.18 > and 1 or 2 fixes in 1.16 or 1.17) should all step up and be release manager > for one of the releases this year. > > Julian > >
Release managers
Calcite needs to make regular releases, and we have established a cadence of every 2 - 3 months that everyone seems to like. But to keep that running, each release needs a release manager, and finding a release manager always seems to be a chore. I wonder if we have trouble recruiting release managers because we only ask for one at a time. How about we get volunteers for the next 5 releases? Then everyone will be seen to be doing their fair share. Release Target date Release manager === === === 1.192019-02 1.202019-04 1.212019-06 1.222019-08 1.232019-10 I propose that frequent committers (anyone who had 2 or more fixes in 1.18 and 1 or 2 fixes in 1.16 or 1.17) should all step up and be release manager for one of the releases this year. Julian
