Release branch has been cut <https://github.com/apache/beam/tree/release-2.24.0>. Reminder: Don't commit to the release branch directly. If you have a fix for a release-blocking issue, contact me to include it as a cherry pick.
Next steps in the process are for me to verify the release branch and to triage release-blocking bugs <https://issues.apache.org/jira/projects/BEAM/versions/12347146>. I've already begun going through bugs and have been leaving comments, so if you have any release-blocking bugs on Jira, please check them. If you have an existing bug that you believe is release-blocking, check it against the requirements in the Beam release guide <https://beam.apache.org/contribute/release-guide/#6-triage-release-blocking-issues-in-jira> first, and if you believe a cherry-pick would be accepted then mark the Jira with "2.24.0" as the fix version and send me the PR that will need to be cherry-picked. On Tue, Aug 11, 2020 at 6:59 PM Daniel Oliveira <[email protected]> wrote: > I'd like to send out a last minute reminder to fill out CHANGES.md > <https://github.com/apache/beam/blob/master/CHANGES.md> with any major > changes that are going to be in 2.24.0. If you need a quick review for > that, just add me as a reviewer to your PR (GitHub username is "youngoli"). > I'll keep an eye out for those until around 5 PM. > > On another note, I need some help with setup from the release guide > <https://beam.apache.org/contribute/release-guide/#one-time-setup-instructions> > : > 1. I need someone to add me as a maintainer of the apache-beam package on > PyPI. Username: danoliveira > 2. Someone might need to create a new version in JIRA > <https://beam.apache.org/contribute/release-guide/#create-a-new-version-in-jira>. > I'm not sure about this one because 2.25.0 already exists, I don't know if > 2.26.0 needs to be created or if that's for the next release. > > On Mon, Aug 10, 2020 at 8:27 PM Daniel Oliveira <[email protected]> > wrote: > >> Hi everyone, >> >> It seems like there's no objections, so I'm preparing to cut the release >> on Wednesday. >> >> As a reminder, if you have any release-blocking issues, please have a >> JIRA and set "Fix version" to 2.24.0. For non-blocking issues, please set >> "Fix version" only once the issue is actually resolved, otherwise it makes >> it more difficult to differentiate release-blocking issues from >> non-blocking. >> >> Thanks, >> Daniel Oliveira >> >> On Thu, Aug 6, 2020 at 4:53 PM Rui Wang <[email protected]> wrote: >> >>> Awesome! >>> >>> >>> -Rui >>> >>> On Thu, Aug 6, 2020 at 4:14 PM Ahmet Altay <[email protected]> wrote: >>> >>>> +1 - Thank you Daniel!! >>>> >>>> On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <[email protected]> >>>> wrote: >>>> >>>>> > You probably meant 2.24.0. >>>>> >>>>> Thanks, yes I did. Mark "Fix Version/s" as "2.24.0" everyone. :) >>>>> >>>>> On Wed, Jul 29, 2020 at 4:14 PM Valentyn Tymofieiev < >>>>> [email protected]> wrote: >>>>> >>>>>> +1, Thanks Daniel! >>>>>> >>>>>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> Hi everyone, >>>>>>> >>>>>>> The next Beam release branch (2.24.0) is scheduled to be cut on >>>>>>> August 12 according to the release calendar [1]. >>>>>>> >>>>>>> I'd like to volunteer to handle this release. Following the lead of >>>>>>> previous release managers, I plan on cutting the branch on that date and >>>>>>> cherrypicking in release-blocking fixes afterwards. So unresolved >>>>>>> release >>>>>>> blocking JIRA issues should have their "Fix Version/s" marked as >>>>>>> "2.23.0". >>>>>>> >>>>>> You probably meant 2.24.0 [1]. >>>>>> >>>>>> >>>>>>> Any comments or objections? >>>>>>> >>>>>>> Thanks, >>>>>>> Daniel Oliveira >>>>>>> >>>>>>> [1] >>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com >>>>>>> >>>>>> [1] https://issues.apache.org/jira/projects/BEAM/versions/12347146 >>>>>> >>>>>
