Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Update: done. going to open the vote as soon as I've gathered the links into the email template On Tue, Apr 13, 2021 at 3:54 PM Kenneth Knowles wrote: > Update: everything is staged except the docker containers. Waiting on > https://issues.apache.org/jira/browse/INFRA-21715 which I forgot to file, > thinking I already had access. > > Kenn > > On Fri, Apr 9, 2021 at 9:30 AM Kenneth Knowles wrote: > >> Update: >> >> - all Jiras with Fix Version = 2.29.0 are resolved >> - all Pull Requests with base=release-2.29.0 are closed >> >> I'm going to proceed and try to get out an RC ASAP. Let me know if there >> is a known critical bug that would make 2.29.0 nonfunctional. >> >> Kenn >> >> On Tue, Mar 30, 2021 at 1:26 PM Brian Hulette >> wrote: >> >>> >>> >>> On Tue, Mar 30, 2021 at 12:16 PM Kenneth Knowles >>> wrote: >>> Update: Based on a number of issues raised, I have re-cut the branch. All Jiras that were resolved to 2.30.0 I have adjusted to 2.29.0. The two remaining issues are: BEAM-11227 "Upgrade beam-vendor-grpc-1_26_0-0.3 to fix CVE-2020-27216": the vendored gRPC has been released and is being debugged. We will cherrypick the upgrade. BEAM-12071 "DataFrame IO sinks do not correctly partition by window": this is not a regression but is a severe problem that makes dataframes unusable; a PR is already up >>> >>> Note this makes DataFrame sinks unusable when used with windowing, not >>> the entire DataFrame API :) >>> PR is here: https://github.com/apache/beam/pull/14374 >>> >>> If you are tracking any issue not mentioned here, be sure to let me know. Kenn On Tue, Mar 16, 2021 at 12:08 PM Kenneth Knowles wrote: > Update: > > There are 5 issues tagged to 2.29.0 release: > https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > There are 4 issues in Needs Triage state with priority P0 or P1: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC > > Kenn > > On Mon, Mar 15, 2021 at 5:01 PM Kenneth Knowles > wrote: > >> Update: >> >> There are 8 issues tagged to 2.29.0 release: >> https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >> >> There are 22 issues in Needs Triage state with priority P0 or P1: >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC >> >> Kenn >> >> On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles >> wrote: >> >>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >>> >>> On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles >>> wrote: >>> Correction: that search did not limit to open issues. There are 17 open. Kenn On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles wrote: > Update: I cut the branch today. > > There are 49 (!) issues with Fix Version = 2.29.0 > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > If you are familiar with any of these, please help me by > determining if it is a critical release-blocking bug or if it is > something > else. > > Kenn > > On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay > wrote: > >> +1 and thank you! >> >> On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles >> wrote: >> >>> Hi All, >>> >>> Beam 2.29.0 release is scheduled to be cut in a week, on March >>> 10 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? >>> >>> Kenn >>> >>> [1] >>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>> >>
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Update: everything is staged except the docker containers. Waiting on https://issues.apache.org/jira/browse/INFRA-21715 which I forgot to file, thinking I already had access. Kenn On Fri, Apr 9, 2021 at 9:30 AM Kenneth Knowles wrote: > Update: > > - all Jiras with Fix Version = 2.29.0 are resolved > - all Pull Requests with base=release-2.29.0 are closed > > I'm going to proceed and try to get out an RC ASAP. Let me know if there > is a known critical bug that would make 2.29.0 nonfunctional. > > Kenn > > On Tue, Mar 30, 2021 at 1:26 PM Brian Hulette wrote: > >> >> >> On Tue, Mar 30, 2021 at 12:16 PM Kenneth Knowles wrote: >> >>> Update: >>> >>> Based on a number of issues raised, I have re-cut the branch. >>> >>> All Jiras that were resolved to 2.30.0 I have adjusted to 2.29.0. >>> >>> The two remaining issues are: >>> >>> BEAM-11227 "Upgrade beam-vendor-grpc-1_26_0-0.3 to fix CVE-2020-27216": >>> the vendored gRPC has been released and is being debugged. We will >>> cherrypick the upgrade. >>> >>> BEAM-12071 "DataFrame IO sinks do not correctly partition by window": >>> this is not a regression but is a severe problem that makes dataframes >>> unusable; a PR is already up >>> >> >> Note this makes DataFrame sinks unusable when used with windowing, not >> the entire DataFrame API :) >> PR is here: https://github.com/apache/beam/pull/14374 >> >> >>> >>> If you are tracking any issue not mentioned here, be sure to let me know. >>> >>> Kenn >>> >>> On Tue, Mar 16, 2021 at 12:08 PM Kenneth Knowles >>> wrote: >>> Update: There are 5 issues tagged to 2.29.0 release: https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC There are 4 issues in Needs Triage state with priority P0 or P1: https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC Kenn On Mon, Mar 15, 2021 at 5:01 PM Kenneth Knowles wrote: > Update: > > There are 8 issues tagged to 2.29.0 release: > https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > There are 22 issues in Needs Triage state with priority P0 or P1: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC > > Kenn > > On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles > wrote: > >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >> >> On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles >> wrote: >> >>> Correction: that search did not limit to open issues. There are 17 >>> open. >>> >>> Kenn >>> >>> On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles >>> wrote: >>> Update: I cut the branch today. There are 49 (!) issues with Fix Version = 2.29.0 https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC If you are familiar with any of these, please help me by determining if it is a critical release-blocking bug or if it is something else. Kenn On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: > +1 and thank you! > > On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles > wrote: > >> Hi All, >> >> Beam 2.29.0 release is scheduled to be cut in a week, on March >> 10 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? >> >> Kenn >> >> [1] >> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >> >
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Update: - all Jiras with Fix Version = 2.29.0 are resolved - all Pull Requests with base=release-2.29.0 are closed I'm going to proceed and try to get out an RC ASAP. Let me know if there is a known critical bug that would make 2.29.0 nonfunctional. Kenn On Tue, Mar 30, 2021 at 1:26 PM Brian Hulette wrote: > > > On Tue, Mar 30, 2021 at 12:16 PM Kenneth Knowles wrote: > >> Update: >> >> Based on a number of issues raised, I have re-cut the branch. >> >> All Jiras that were resolved to 2.30.0 I have adjusted to 2.29.0. >> >> The two remaining issues are: >> >> BEAM-11227 "Upgrade beam-vendor-grpc-1_26_0-0.3 to fix CVE-2020-27216": >> the vendored gRPC has been released and is being debugged. We will >> cherrypick the upgrade. >> >> BEAM-12071 "DataFrame IO sinks do not correctly partition by window": >> this is not a regression but is a severe problem that makes dataframes >> unusable; a PR is already up >> > > Note this makes DataFrame sinks unusable when used with windowing, not the > entire DataFrame API :) > PR is here: https://github.com/apache/beam/pull/14374 > > >> >> If you are tracking any issue not mentioned here, be sure to let me know. >> >> Kenn >> >> On Tue, Mar 16, 2021 at 12:08 PM Kenneth Knowles wrote: >> >>> Update: >>> >>> There are 5 issues tagged to 2.29.0 release: >>> https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >>> >>> There are 4 issues in Needs Triage state with priority P0 or P1: >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC >>> >>> Kenn >>> >>> On Mon, Mar 15, 2021 at 5:01 PM Kenneth Knowles wrote: >>> Update: There are 8 issues tagged to 2.29.0 release: https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC There are 22 issues in Needs Triage state with priority P0 or P1: https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC Kenn On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles > wrote: > >> Correction: that search did not limit to open issues. There are 17 >> open. >> >> Kenn >> >> On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles >> wrote: >> >>> Update: I cut the branch today. >>> >>> There are 49 (!) issues with Fix Version = 2.29.0 >>> >>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >>> >>> If you are familiar with any of these, please help me by determining >>> if it is a critical release-blocking bug or if it is something else. >>> >>> Kenn >>> >>> On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay >>> wrote: >>> +1 and thank you! On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles wrote: > Hi All, > > Beam 2.29.0 release is scheduled to be cut in a week, on March 10 > 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? > > Kenn > > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
On Tue, Mar 30, 2021 at 12:16 PM Kenneth Knowles wrote: > Update: > > Based on a number of issues raised, I have re-cut the branch. > > All Jiras that were resolved to 2.30.0 I have adjusted to 2.29.0. > > The two remaining issues are: > > BEAM-11227 "Upgrade beam-vendor-grpc-1_26_0-0.3 to fix CVE-2020-27216": > the vendored gRPC has been released and is being debugged. We will > cherrypick the upgrade. > > BEAM-12071 "DataFrame IO sinks do not correctly partition by window": this > is not a regression but is a severe problem that makes dataframes unusable; > a PR is already up > Note this makes DataFrame sinks unusable when used with windowing, not the entire DataFrame API :) PR is here: https://github.com/apache/beam/pull/14374 > > If you are tracking any issue not mentioned here, be sure to let me know. > > Kenn > > On Tue, Mar 16, 2021 at 12:08 PM Kenneth Knowles wrote: > >> Update: >> >> There are 5 issues tagged to 2.29.0 release: >> https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >> >> There are 4 issues in Needs Triage state with priority P0 or P1: >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC >> >> Kenn >> >> On Mon, Mar 15, 2021 at 5:01 PM Kenneth Knowles wrote: >> >>> Update: >>> >>> There are 8 issues tagged to 2.29.0 release: >>> https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >>> >>> There are 22 issues in Needs Triage state with priority P0 or P1: >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC >>> >>> Kenn >>> >>> On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: > Correction: that search did not limit to open issues. There are 17 > open. > > Kenn > > On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles > wrote: > >> Update: I cut the branch today. >> >> There are 49 (!) issues with Fix Version = 2.29.0 >> >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >> >> If you are familiar with any of these, please help me by determining >> if it is a critical release-blocking bug or if it is something else. >> >> Kenn >> >> On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: >> >>> +1 and thank you! >>> >>> On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles >>> wrote: >>> Hi All, Beam 2.29.0 release is scheduled to be cut in a week, on March 10 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? Kenn [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>>
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Update: Based on a number of issues raised, I have re-cut the branch. All Jiras that were resolved to 2.30.0 I have adjusted to 2.29.0. The two remaining issues are: BEAM-11227 "Upgrade beam-vendor-grpc-1_26_0-0.3 to fix CVE-2020-27216": the vendored gRPC has been released and is being debugged. We will cherrypick the upgrade. BEAM-12071 "DataFrame IO sinks do not correctly partition by window": this is not a regression but is a severe problem that makes dataframes unusable; a PR is already up If you are tracking any issue not mentioned here, be sure to let me know. Kenn On Tue, Mar 16, 2021 at 12:08 PM Kenneth Knowles wrote: > Update: > > There are 5 issues tagged to 2.29.0 release: > https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > There are 4 issues in Needs Triage state with priority P0 or P1: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC > > Kenn > > On Mon, Mar 15, 2021 at 5:01 PM Kenneth Knowles wrote: > >> Update: >> >> There are 8 issues tagged to 2.29.0 release: >> https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >> >> There are 22 issues in Needs Triage state with priority P0 or P1: >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC >> >> Kenn >> >> On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: >> >>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >>> >>> On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: >>> Correction: that search did not limit to open issues. There are 17 open. Kenn On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles wrote: > Update: I cut the branch today. > > There are 49 (!) issues with Fix Version = 2.29.0 > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > If you are familiar with any of these, please help me by determining > if it is a critical release-blocking bug or if it is something else. > > Kenn > > On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: > >> +1 and thank you! >> >> On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles >> wrote: >> >>> Hi All, >>> >>> Beam 2.29.0 release is scheduled to be cut in a week, on March 10 >>> 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? >>> >>> Kenn >>> >>> [1] >>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>> >>
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Update: There are 5 issues tagged to 2.29.0 release: https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC There are 4 issues in Needs Triage state with priority P0 or P1: https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC Kenn On Mon, Mar 15, 2021 at 5:01 PM Kenneth Knowles wrote: > Update: > > There are 8 issues tagged to 2.29.0 release: > https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > There are 22 issues in Needs Triage state with priority P0 or P1: > https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC > > Kenn > > On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: > >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >> >> On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: >> >>> Correction: that search did not limit to open issues. There are 17 open. >>> >>> Kenn >>> >>> On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles wrote: >>> Update: I cut the branch today. There are 49 (!) issues with Fix Version = 2.29.0 https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC If you are familiar with any of these, please help me by determining if it is a critical release-blocking bug or if it is something else. Kenn On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: > +1 and thank you! > > On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles > wrote: > >> Hi All, >> >> Beam 2.29.0 release is scheduled to be cut in a week, on March 10 >> 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? >> >> Kenn >> >> [1] >> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >> >
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Update: There are 8 issues tagged to 2.29.0 release: https://issues.apache.org/jira/issues/?jql=statusCategory%20!%3D%20done%20AND%20project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC There are 22 issues in Needs Triage state with priority P0 or P1: https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20status%20%3D%20%22Triage%20Needed%22%20AND%20priority%20in%20(P0%2C%20P1)%20ORDER%20BY%20updated%20DESC Kenn On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: > >> Correction: that search did not limit to open issues. There are 17 open. >> >> Kenn >> >> On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles wrote: >> >>> Update: I cut the branch today. >>> >>> There are 49 (!) issues with Fix Version = 2.29.0 >>> >>> >>> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >>> >>> If you are familiar with any of these, please help me by determining if >>> it is a critical release-blocking bug or if it is something else. >>> >>> Kenn >>> >>> On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: >>> +1 and thank you! On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles wrote: > Hi All, > > Beam 2.29.0 release is scheduled to be cut in a week, on March 10 > 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? > > Kenn > > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20AND%20statusCategory%20%3D%20%22To%20Do%22%20%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC On Thu, Mar 11, 2021 at 8:43 PM Kenneth Knowles wrote: > Correction: that search did not limit to open issues. There are 17 open. > > Kenn > > On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles wrote: > >> Update: I cut the branch today. >> >> There are 49 (!) issues with Fix Version = 2.29.0 >> >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC >> >> If you are familiar with any of these, please help me by determining if >> it is a critical release-blocking bug or if it is something else. >> >> Kenn >> >> On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: >> >>> +1 and thank you! >>> >>> On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles wrote: >>> Hi All, Beam 2.29.0 release is scheduled to be cut in a week, on March 10 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? Kenn [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>>
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Correction: that search did not limit to open issues. There are 17 open. Kenn On Thu, Mar 11, 2021 at 8:42 PM Kenneth Knowles wrote: > Update: I cut the branch today. > > There are 49 (!) issues with Fix Version = 2.29.0 > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC > > If you are familiar with any of these, please help me by determining if it > is a critical release-blocking bug or if it is something else. > > Kenn > > On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: > >> +1 and thank you! >> >> On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles wrote: >> >>> Hi All, >>> >>> Beam 2.29.0 release is scheduled to be cut in a week, on March 10 >>> 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? >>> >>> Kenn >>> >>> [1] >>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >>> >>
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
Update: I cut the branch today. There are 49 (!) issues with Fix Version = 2.29.0 https://issues.apache.org/jira/issues/?jql=project%20%3D%2012319527%20AND%20fixVersion%20%3D%2012349629%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC If you are familiar with any of these, please help me by determining if it is a critical release-blocking bug or if it is something else. Kenn On Wed, Mar 3, 2021 at 11:53 AM Ahmet Altay wrote: > +1 and thank you! > > On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles wrote: > >> Hi All, >> >> Beam 2.29.0 release is scheduled to be cut in a week, on March 10 >> 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? >> >> Kenn >> >> [1] >> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >> >
Re: [PROPOSAL] Preparing for Beam 2.29.0 release
+1 and thank you! On Wed, Mar 3, 2021 at 11:51 AM Kenneth Knowles wrote: > Hi All, > > Beam 2.29.0 release is scheduled to be cut in a week, on March 10 > 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? > > Kenn > > [1] > https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles >
[PROPOSAL] Preparing for Beam 2.29.0 release
Hi All, Beam 2.29.0 release is scheduled to be cut in a week, on March 10 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? Kenn [1] https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com=America/Los_Angeles
