Re: [PROPOSAL] Preparing for Beam 2.30.0 release
Please note that I created https://issues.apache.org/jira/browse/BEAM-12338 as a potential blocker. Fix was merged to master and sent a cherry-pick: https://github.com/apache/beam/pull/14821 Thanks, Cham On Fri, May 14, 2021 at 7:59 AM Evan Galpin wrote: > Not sure if it's on the radar but there was mention on this Reshuffle > PR[1] of cherry-picking it to 2.30.0 > > [1] https://github.com/apache/beam/pull/14720 > > Thanks, > Evan > > On Thu, May 13, 2021 at 6:50 PM Heejong Lee wrote: > >> UPDATE: >> >> All precommit and postcommit tests are passed now: >> https://github.com/apache/beam/pull/14711 >> >> We only have one open issue for Fix Version 2.30.0: >> https://issues.apache.org/jira/browse/BEAM-12242?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.30.0 >> >> I will start building the RC release after we cherry-pick the last >> blocker. >> >> On Thu, Apr 29, 2021 at 12:48 AM Heejong Lee wrote: >> >>> We have 10 open issues for Fix Version 2.30.0: >>> https://issues.apache.org/jira/browse/BEAM-12242?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.30.0 >>> >>> On Thu, Apr 29, 2021 at 12:30 AM Heejong Lee wrote: >>> FYI, I just cut the 2.30.0 release branch. From now on, late commits for 2.30.0 need to be cherry-picked. If you have any late commits, please make sure that their Jira issues have the correct Fix Version, 2.30.0. On Tue, Apr 27, 2021 at 7:52 AM Kenneth Knowles wrote: > SGTM. Thanks! > > On Mon, Apr 26, 2021 at 2:33 PM Heejong Lee > wrote: > >> >> >> On Mon, Apr 26, 2021 at 10:24 AM Robert Bradshaw >> wrote: >> >>> Confirming that the cut date is 4/28/2021 (in two days), right? >>> >> >> Yes, 2.30.0 branch is scheduled to be cut on April 28. >> >> >>> >>> On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki >>> wrote: >>> > >>> > Thank you for the preparation! >>> > >>> > > a few responses that some high priority changes >>> > >>> > Would you be willing to share the items for visibility? >>> >>> There are several PRs in flight (or recently merged) to get >>> portability working well with Dataflow for this release. >>> >> >> We can still cherry-pick them by importance after the branch cut. >> >> >>> >>> > >>> > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles >>> wrote: >>> > > >>> > > Also the 2.29.0 was re-cut. >>> > > >>> > > Usually a delay in one release should not delay the next >>> release, because each release represents a certain quantity of changes. >>> But >>> in this case, the actual quantity of changes is affected by the re-cut, >>> too. >>> > > >>> > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee >>> wrote: >>> > >> >>> > >> Update on the 2.30.0 branch cut schedule: >>> > >> >>> > >> I'm thinking of delaying the branch cut a week since I've got a >>> few responses that some high priority changes are still ongoing. >>> > >> >>> > >> The new cut date is April 28. >>> > >> >>> > >> >>> > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay >>> wrote: >>> > >>> >>> > >>> +1 and thank you! >>> > >>> >>> > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee < >>> heej...@google.com> wrote: >>> > >>> > Hi All, >>> > >>> > Beam 2.30.0 release is scheduled to be cut on April 21 >>> according to the release calendar [1] >>> > >>> > I'd like to volunteer myself to be the release manager for >>> this release. I plan on cutting the release branch on the scheduled >>> date. >>> > >>> > Any comments or objections ? >>> > >>> > Thanks, >>> > Heejong >>> > >>> > [1] >>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>> > >>> > >>> > >>> > -- >>> > Regards, >>> > Tomo >>> >>
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
Not sure if it's on the radar but there was mention on this Reshuffle PR[1] of cherry-picking it to 2.30.0 [1] https://github.com/apache/beam/pull/14720 Thanks, Evan On Thu, May 13, 2021 at 6:50 PM Heejong Lee wrote: > UPDATE: > > All precommit and postcommit tests are passed now: > https://github.com/apache/beam/pull/14711 > > We only have one open issue for Fix Version 2.30.0: > https://issues.apache.org/jira/browse/BEAM-12242?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.30.0 > > I will start building the RC release after we cherry-pick the last blocker. > > On Thu, Apr 29, 2021 at 12:48 AM Heejong Lee wrote: > >> We have 10 open issues for Fix Version 2.30.0: >> https://issues.apache.org/jira/browse/BEAM-12242?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.30.0 >> >> On Thu, Apr 29, 2021 at 12:30 AM Heejong Lee wrote: >> >>> FYI, I just cut the 2.30.0 release branch. From now on, late commits for >>> 2.30.0 need to be cherry-picked. If you have any late commits, please make >>> sure that their Jira issues have the correct Fix Version, 2.30.0. >>> >>> On Tue, Apr 27, 2021 at 7:52 AM Kenneth Knowles wrote: >>> SGTM. Thanks! On Mon, Apr 26, 2021 at 2:33 PM Heejong Lee wrote: > > > On Mon, Apr 26, 2021 at 10:24 AM Robert Bradshaw > wrote: > >> Confirming that the cut date is 4/28/2021 (in two days), right? >> > > Yes, 2.30.0 branch is scheduled to be cut on April 28. > > >> >> On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki >> wrote: >> > >> > Thank you for the preparation! >> > >> > > a few responses that some high priority changes >> > >> > Would you be willing to share the items for visibility? >> >> There are several PRs in flight (or recently merged) to get >> portability working well with Dataflow for this release. >> > > We can still cherry-pick them by importance after the branch cut. > > >> >> > >> > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles >> wrote: >> > > >> > > Also the 2.29.0 was re-cut. >> > > >> > > Usually a delay in one release should not delay the next release, >> because each release represents a certain quantity of changes. But in >> this >> case, the actual quantity of changes is affected by the re-cut, too. >> > > >> > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee >> wrote: >> > >> >> > >> Update on the 2.30.0 branch cut schedule: >> > >> >> > >> I'm thinking of delaying the branch cut a week since I've got a >> few responses that some high priority changes are still ongoing. >> > >> >> > >> The new cut date is April 28. >> > >> >> > >> >> > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay >> wrote: >> > >>> >> > >>> +1 and thank you! >> > >>> >> > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee >> wrote: >> > >> > Hi All, >> > >> > Beam 2.30.0 release is scheduled to be cut on April 21 >> according to the release calendar [1] >> > >> > I'd like to volunteer myself to be the release manager for >> this release. I plan on cutting the release branch on the scheduled date. >> > >> > Any comments or objections ? >> > >> > Thanks, >> > Heejong >> > >> > [1] >> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >> > >> > >> > >> > -- >> > Regards, >> > Tomo >> >
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
UPDATE: All precommit and postcommit tests are passed now: https://github.com/apache/beam/pull/14711 We only have one open issue for Fix Version 2.30.0: https://issues.apache.org/jira/browse/BEAM-12242?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.30.0 I will start building the RC release after we cherry-pick the last blocker. On Thu, Apr 29, 2021 at 12:48 AM Heejong Lee wrote: > We have 10 open issues for Fix Version 2.30.0: > https://issues.apache.org/jira/browse/BEAM-12242?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.30.0 > > On Thu, Apr 29, 2021 at 12:30 AM Heejong Lee wrote: > >> FYI, I just cut the 2.30.0 release branch. From now on, late commits for >> 2.30.0 need to be cherry-picked. If you have any late commits, please make >> sure that their Jira issues have the correct Fix Version, 2.30.0. >> >> On Tue, Apr 27, 2021 at 7:52 AM Kenneth Knowles wrote: >> >>> SGTM. Thanks! >>> >>> On Mon, Apr 26, 2021 at 2:33 PM Heejong Lee wrote: >>> On Mon, Apr 26, 2021 at 10:24 AM Robert Bradshaw wrote: > Confirming that the cut date is 4/28/2021 (in two days), right? > Yes, 2.30.0 branch is scheduled to be cut on April 28. > > On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki > wrote: > > > > Thank you for the preparation! > > > > > a few responses that some high priority changes > > > > Would you be willing to share the items for visibility? > > There are several PRs in flight (or recently merged) to get > portability working well with Dataflow for this release. > We can still cherry-pick them by importance after the branch cut. > > > > > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles > wrote: > > > > > > Also the 2.29.0 was re-cut. > > > > > > Usually a delay in one release should not delay the next release, > because each release represents a certain quantity of changes. But in this > case, the actual quantity of changes is affected by the re-cut, too. > > > > > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee > wrote: > > >> > > >> Update on the 2.30.0 branch cut schedule: > > >> > > >> I'm thinking of delaying the branch cut a week since I've got a > few responses that some high priority changes are still ongoing. > > >> > > >> The new cut date is April 28. > > >> > > >> > > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay > wrote: > > >>> > > >>> +1 and thank you! > > >>> > > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee > wrote: > > > > Hi All, > > > > Beam 2.30.0 release is scheduled to be cut on April 21 > according to the release calendar [1] > > > > I'd like to volunteer myself to be the release manager for this > release. I plan on cutting the release branch on the scheduled date. > > > > Any comments or objections ? > > > > Thanks, > > Heejong > > > > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles > > > > > > > > -- > > Regards, > > Tomo >
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
We have 10 open issues for Fix Version 2.30.0: https://issues.apache.org/jira/browse/BEAM-12242?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.30.0 On Thu, Apr 29, 2021 at 12:30 AM Heejong Lee wrote: > FYI, I just cut the 2.30.0 release branch. From now on, late commits for > 2.30.0 need to be cherry-picked. If you have any late commits, please make > sure that their Jira issues have the correct Fix Version, 2.30.0. > > On Tue, Apr 27, 2021 at 7:52 AM Kenneth Knowles wrote: > >> SGTM. Thanks! >> >> On Mon, Apr 26, 2021 at 2:33 PM Heejong Lee wrote: >> >>> >>> >>> On Mon, Apr 26, 2021 at 10:24 AM Robert Bradshaw >>> wrote: >>> Confirming that the cut date is 4/28/2021 (in two days), right? >>> >>> Yes, 2.30.0 branch is scheduled to be cut on April 28. >>> >>> On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki wrote: > > Thank you for the preparation! > > > a few responses that some high priority changes > > Would you be willing to share the items for visibility? There are several PRs in flight (or recently merged) to get portability working well with Dataflow for this release. >>> >>> We can still cherry-pick them by importance after the branch cut. >>> >>> > > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles wrote: > > > > Also the 2.29.0 was re-cut. > > > > Usually a delay in one release should not delay the next release, because each release represents a certain quantity of changes. But in this case, the actual quantity of changes is affected by the re-cut, too. > > > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee wrote: > >> > >> Update on the 2.30.0 branch cut schedule: > >> > >> I'm thinking of delaying the branch cut a week since I've got a few responses that some high priority changes are still ongoing. > >> > >> The new cut date is April 28. > >> > >> > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay wrote: > >>> > >>> +1 and thank you! > >>> > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee wrote: > > Hi All, > > Beam 2.30.0 release is scheduled to be cut on April 21 according to the release calendar [1] > > I'd like to volunteer myself to be the release manager for this release. I plan on cutting the release branch on the scheduled date. > > Any comments or objections ? > > Thanks, > Heejong > > [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles > > > > -- > Regards, > Tomo >>>
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
FYI, I just cut the 2.30.0 release branch. From now on, late commits for 2.30.0 need to be cherry-picked. If you have any late commits, please make sure that their Jira issues have the correct Fix Version, 2.30.0. On Tue, Apr 27, 2021 at 7:52 AM Kenneth Knowles wrote: > SGTM. Thanks! > > On Mon, Apr 26, 2021 at 2:33 PM Heejong Lee wrote: > >> >> >> On Mon, Apr 26, 2021 at 10:24 AM Robert Bradshaw >> wrote: >> >>> Confirming that the cut date is 4/28/2021 (in two days), right? >>> >> >> Yes, 2.30.0 branch is scheduled to be cut on April 28. >> >> >>> >>> On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki wrote: >>> > >>> > Thank you for the preparation! >>> > >>> > > a few responses that some high priority changes >>> > >>> > Would you be willing to share the items for visibility? >>> >>> There are several PRs in flight (or recently merged) to get >>> portability working well with Dataflow for this release. >>> >> >> We can still cherry-pick them by importance after the branch cut. >> >> >>> >>> > >>> > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles >>> wrote: >>> > > >>> > > Also the 2.29.0 was re-cut. >>> > > >>> > > Usually a delay in one release should not delay the next release, >>> because each release represents a certain quantity of changes. But in this >>> case, the actual quantity of changes is affected by the re-cut, too. >>> > > >>> > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee >>> wrote: >>> > >> >>> > >> Update on the 2.30.0 branch cut schedule: >>> > >> >>> > >> I'm thinking of delaying the branch cut a week since I've got a few >>> responses that some high priority changes are still ongoing. >>> > >> >>> > >> The new cut date is April 28. >>> > >> >>> > >> >>> > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay >>> wrote: >>> > >>> >>> > >>> +1 and thank you! >>> > >>> >>> > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee >>> wrote: >>> > >>> > Hi All, >>> > >>> > Beam 2.30.0 release is scheduled to be cut on April 21 according >>> to the release calendar [1] >>> > >>> > I'd like to volunteer myself to be the release manager for this >>> release. I plan on cutting the release branch on the scheduled date. >>> > >>> > Any comments or objections ? >>> > >>> > Thanks, >>> > Heejong >>> > >>> > [1] >>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>> > >>> > >>> > >>> > -- >>> > Regards, >>> > Tomo >>> >>
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
SGTM. Thanks! On Mon, Apr 26, 2021 at 2:33 PM Heejong Lee wrote: > > > On Mon, Apr 26, 2021 at 10:24 AM Robert Bradshaw > wrote: > >> Confirming that the cut date is 4/28/2021 (in two days), right? >> > > Yes, 2.30.0 branch is scheduled to be cut on April 28. > > >> >> On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki wrote: >> > >> > Thank you for the preparation! >> > >> > > a few responses that some high priority changes >> > >> > Would you be willing to share the items for visibility? >> >> There are several PRs in flight (or recently merged) to get >> portability working well with Dataflow for this release. >> > > We can still cherry-pick them by importance after the branch cut. > > >> >> > >> > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles >> wrote: >> > > >> > > Also the 2.29.0 was re-cut. >> > > >> > > Usually a delay in one release should not delay the next release, >> because each release represents a certain quantity of changes. But in this >> case, the actual quantity of changes is affected by the re-cut, too. >> > > >> > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee >> wrote: >> > >> >> > >> Update on the 2.30.0 branch cut schedule: >> > >> >> > >> I'm thinking of delaying the branch cut a week since I've got a few >> responses that some high priority changes are still ongoing. >> > >> >> > >> The new cut date is April 28. >> > >> >> > >> >> > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay >> wrote: >> > >>> >> > >>> +1 and thank you! >> > >>> >> > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee >> wrote: >> > >> > Hi All, >> > >> > Beam 2.30.0 release is scheduled to be cut on April 21 according >> to the release calendar [1] >> > >> > I'd like to volunteer myself to be the release manager for this >> release. I plan on cutting the release branch on the scheduled date. >> > >> > Any comments or objections ? >> > >> > Thanks, >> > Heejong >> > >> > [1] >> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >> > >> > >> > >> > -- >> > Regards, >> > Tomo >> >
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
On Mon, Apr 26, 2021 at 10:24 AM Robert Bradshaw wrote: > Confirming that the cut date is 4/28/2021 (in two days), right? > Yes, 2.30.0 branch is scheduled to be cut on April 28. > > On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki wrote: > > > > Thank you for the preparation! > > > > > a few responses that some high priority changes > > > > Would you be willing to share the items for visibility? > > There are several PRs in flight (or recently merged) to get > portability working well with Dataflow for this release. > We can still cherry-pick them by importance after the branch cut. > > > > > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles wrote: > > > > > > Also the 2.29.0 was re-cut. > > > > > > Usually a delay in one release should not delay the next release, > because each release represents a certain quantity of changes. But in this > case, the actual quantity of changes is affected by the re-cut, too. > > > > > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee > wrote: > > >> > > >> Update on the 2.30.0 branch cut schedule: > > >> > > >> I'm thinking of delaying the branch cut a week since I've got a few > responses that some high priority changes are still ongoing. > > >> > > >> The new cut date is April 28. > > >> > > >> > > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay wrote: > > >>> > > >>> +1 and thank you! > > >>> > > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee > wrote: > > > > Hi All, > > > > Beam 2.30.0 release is scheduled to be cut on April 21 according to > the release calendar [1] > > > > I'd like to volunteer myself to be the release manager for this > release. I plan on cutting the release branch on the scheduled date. > > > > Any comments or objections ? > > > > Thanks, > > Heejong > > > > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles > > > > > > > > -- > > Regards, > > Tomo >
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
Confirming that the cut date is 4/28/2021 (in two days), right? On Wed, Apr 21, 2021 at 4:41 PM Tomo Suzuki wrote: > > Thank you for the preparation! > > > a few responses that some high priority changes > > Would you be willing to share the items for visibility? There are several PRs in flight (or recently merged) to get portability working well with Dataflow for this release. > > On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles wrote: > > > > Also the 2.29.0 was re-cut. > > > > Usually a delay in one release should not delay the next release, because > > each release represents a certain quantity of changes. But in this case, > > the actual quantity of changes is affected by the re-cut, too. > > > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee wrote: > >> > >> Update on the 2.30.0 branch cut schedule: > >> > >> I'm thinking of delaying the branch cut a week since I've got a few > >> responses that some high priority changes are still ongoing. > >> > >> The new cut date is April 28. > >> > >> > >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay wrote: > >>> > >>> +1 and thank you! > >>> > >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee wrote: > > Hi All, > > Beam 2.30.0 release is scheduled to be cut on April 21 according to the > release calendar [1] > > I'd like to volunteer myself to be the release manager for this release. > I plan on cutting the release branch on the scheduled date. > > Any comments or objections ? > > Thanks, > Heejong > > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles > > > > -- > Regards, > Tomo
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
Thank you for the preparation! > a few responses that some high priority changes Would you be willing to share the items for visibility? On Wed, Apr 21, 2021 at 7:21 PM Kenneth Knowles wrote: > > Also the 2.29.0 was re-cut. > > Usually a delay in one release should not delay the next release, because > each release represents a certain quantity of changes. But in this case, the > actual quantity of changes is affected by the re-cut, too. > > On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee wrote: >> >> Update on the 2.30.0 branch cut schedule: >> >> I'm thinking of delaying the branch cut a week since I've got a few >> responses that some high priority changes are still ongoing. >> >> The new cut date is April 28. >> >> >> On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay wrote: >>> >>> +1 and thank you! >>> >>> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee wrote: Hi All, Beam 2.30.0 release is scheduled to be cut on April 21 according to the release calendar [1] I'd like to volunteer myself to be the release manager for this release. I plan on cutting the release branch on the scheduled date. Any comments or objections ? Thanks, Heejong [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles -- Regards, Tomo
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
Also the 2.29.0 was re-cut. Usually a delay in one release should not delay the next release, because each release represents a certain quantity of changes. But in this case, the actual quantity of changes is affected by the re-cut, too. On Wed, Apr 21, 2021 at 4:12 PM Heejong Lee wrote: > Update on the 2.30.0 branch cut schedule: > > I'm thinking of delaying the branch cut a week since I've got a few > responses that some high priority changes are still ongoing. > > The new cut date is April 28. > > > On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay wrote: > >> +1 and thank you! >> >> On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee wrote: >> >>> Hi All, >>> >>> Beam 2.30.0 release is scheduled to be cut on April 21 according to the >>> release calendar [1] >>> >>> I'd like to volunteer myself to be the release manager for this release. >>> I plan on cutting the release branch on the scheduled date. >>> >>> Any comments or objections ? >>> >>> Thanks, >>> Heejong >>> >>> [1] >>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>> >>
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
Update on the 2.30.0 branch cut schedule: I'm thinking of delaying the branch cut a week since I've got a few responses that some high priority changes are still ongoing. The new cut date is April 28. On Tue, Apr 20, 2021 at 6:07 PM Ahmet Altay wrote: > +1 and thank you! > > On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee wrote: > >> Hi All, >> >> Beam 2.30.0 release is scheduled to be cut on April 21 according to the >> release calendar [1] >> >> I'd like to volunteer myself to be the release manager for this release. >> I plan on cutting the release branch on the scheduled date. >> >> Any comments or objections ? >> >> Thanks, >> Heejong >> >> [1] >> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >> >
Re: [PROPOSAL] Preparing for Beam 2.30.0 release
+1 and thank you! On Tue, Apr 20, 2021 at 4:55 PM Heejong Lee wrote: > Hi All, > > Beam 2.30.0 release is scheduled to be cut on April 21 according to the > release calendar [1] > > I'd like to volunteer myself to be the release manager for this release. > I plan on cutting the release branch on the scheduled date. > > Any comments or objections ? > > Thanks, > Heejong > > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >
[PROPOSAL] Preparing for Beam 2.30.0 release
Hi All, Beam 2.30.0 release is scheduled to be cut on April 21 according to the release calendar [1] I'd like to volunteer myself to be the release manager for this release. I plan on cutting the release branch on the scheduled date. Any comments or objections ? Thanks, Heejong [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles
