I'm waiting for these last 4 issues ( https://github.com/apache/beam/milestone/12) which have associated PRs to get merged and I'll cut the branch after that.
On Wed, May 17, 2023 at 12:23 PM Ritesh Ghorse <riteshgho...@google.com> wrote: > To get the release going, > Could a PMC member help me by adding my key to > https://dist.apache.org/repos/dist/release/beam/KEYS? I've appended my > key to https://dist.apache.org/repos/dist/dev/beam/KEYS. > > Also, could someone please add me (username: riteshghorse) to the > maintainers group at https://pypi.org/project/apache-beam/ > > Thanks! > > On Mon, May 8, 2023 at 11:25 AM Anand Inguva <ananding...@google.com> > wrote: > >> Thanks. I will add this as a milestone to 2.49.0. >> >> On Mon, May 8, 2023 at 11:21 AM Valentyn Tymofieiev <valen...@google.com> >> wrote: >> >>> > Absent a compelling reason otherwise, my view would be to just stick >>> with the statement of dropping it as soon as it goes out of support >>> >>> This is the process we agreed upon last time we discussed the version >>> support policy on dev@. >>> >>> On Fri, May 5, 2023 at 6:18 PM Robert Bradshaw via dev < >>> dev@beam.apache.org> wrote: >>> >>>> On Fri, May 5, 2023 at 6:27 AM Anand Inguva via dev < >>>> dev@beam.apache.org> wrote: >>>> > >>>> > >> Is there a significant gain in dropping 3.7 support before the cut? >>>> > >>>> > No, I think it is just a matter of how soon we want to do it. >>>> >>>> Absent a compelling reason otherwise, my view would be to just stick >>>> with the statement of dropping it as soon as it goes out of support, >>>> but not sooner. Yeah, it's only a matter of a couple of weeks, but the >>>> subsequent release isn't far behind. >>>> >>>> > On Thu, May 4, 2023 at 12:11 PM Ritesh Ghorse < >>>> riteshgho...@google.com> wrote: >>>> >> >>>> >> +1 to get target for 2.48.0 >>>> >> >>>> >> On Thu, May 4, 2023 at 11:33 AM Jack McCluskey via dev < >>>> dev@beam.apache.org> wrote: >>>> >>> >>>> >>> I'd suggest shooting for 2.48.0 so we're ahead of the >>>> end-of-support date. We're also supporting 5 different Python versions in >>>> 2.47.0, it's probably for the best to try and pare that down. >>>> >>> >>>> >>> On Thu, May 4, 2023 at 11:25 AM Anand Inguva via dev < >>>> dev@beam.apache.org> wrote: >>>> >>>> >>>> >>>> Thanks Ritesh!! >>>> >>>> >>>> >>>> Python 3.7 support is going to end on June 27th 2023. Beam 2.48.0 >>>> may get released ~1-2 weeks earlier of that date. >>>> >>>> >>>> >>>> My question here is should we target 2.48.0 or 2.49.0 to stop >>>> supporting Python 3.7 for beam? >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Anand >>>> >>>> >>>> >>>> On Wed, May 3, 2023 at 10:25 PM Jeff Zhang <zjf...@gmail.com> >>>> wrote: >>>> >>>>> >>>> >>>>> Thank you! @Ahmet Altay >>>> >>>>> >>>> >>>>> On Thu, May 4, 2023 at 10:17 AM Ahmet Altay <al...@google.com> >>>> wrote: >>>> >>>>>> >>>> >>>>>> It is every 6 weeks. There is also a published calendar for >>>> release branch cut dates: >>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com&ctz=America/Los_Angeles >>>> >>>>>> >>>> >>>>>> On Wed, May 3, 2023 at 10:13 PM Jeff Zhang <zjf...@gmail.com> >>>> wrote: >>>> >>>>>>> >>>> >>>>>>> I just saw another thread about the vote of 2.47.0 release, >>>> just curious to know what is beam's release cadence, is it monthly? >>>> >>>>>>> >>>> >>>>>>> >>>> >>>>>>> On Thu, May 4, 2023 at 1:58 AM Kenneth Knowles <k...@apache.org> >>>> wrote: >>>> >>>>>>>> >>>> >>>>>>>> Excellent, thank you! >>>> >>>>>>>> >>>> >>>>>>>> On Wed, May 3, 2023 at 7:21 AM Ahmet Altay via dev < >>>> dev@beam.apache.org> wrote: >>>> >>>>>>>>> >>>> >>>>>>>>> Thank you Ritesh! >>>> >>>>>>>>> >>>> >>>>>>>>> On Wed, May 3, 2023 at 10:00 AM Ritesh Ghorse via dev < >>>> dev@beam.apache.org> wrote: >>>> >>>>>>>>>> >>>> >>>>>>>>>> Hey everyone, >>>> >>>>>>>>>> >>>> >>>>>>>>>> The next release branch 2.48.0 cut is scheduled for May >>>> 17th, according to >>>> >>>>>>>>>> the release calendar [1]. >>>> >>>>>>>>>> >>>> >>>>>>>>>> I would like to volunteer myself to do this release. I'll >>>> cut the branch on the scheduled date, and cherrypick release-blocking fixes >>>> later. >>>> >>>>>>>>>> >>>> >>>>>>>>>> Please help me make sure the release goes smoothly by: >>>> >>>>>>>>>> - Making sure that any unresolved release blocking issues >>>> for 2.48.0 have their "Milestone" marked as "2.48.0 Release". >>>> >>>>>>>>>> - Reviewing the current release blockers [2] and remove the >>>> Milestone if they don't meet the criteria at [3]. >>>> >>>>>>>>>> >>>> >>>>>>>>>> [1] >>>> https://calendar.google.com/calendar/u/0/embed?src=0p73sl034k80oob7seouani...@group.calendar.google.com >>>> >>>>>>>>>> [2] https://github.com/apache/beam/milestone/12 >>>> >>>>>>>>>> [3] https://beam.apache.org/contribute/release-blocking/ >>>> >>>>>>>>>> >>>> >>>>>>>>>> Thanks! >>>> >>>>>>>>>> >>>> >>>>>>>>>> -- >>>> >>>>>>>>>> Regards, >>>> >>>>>>>>>> Ritesh Ghorse >>>> >>>>>>> >>>> >>>>>>> >>>> >>>>>>> >>>> >>>>>>> -- >>>> >>>>>>> Best Regards >>>> >>>>>>> >>>> >>>>>>> Jeff Zhang >>>> >>>>> >>>> >>>>> >>>> >>>>> >>>> >>>>> -- >>>> >>>>> Best Regards >>>> >>>>> >>>> >>>>> Jeff Zhang >>>> >>>
