Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Ahmet Altay <al...@google.com>]

+1 - Thank you Daniel!!

On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <da...@google.com>
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 <va...@google.com>
> wrote:
>
>> +1, Thanks Daniel!
>>
>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira <da...@google.com>
>> 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
>>
>

Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Daniel Oliveira <da...@google.com>]

I just sent out an update on the RC3 vote thread, and in it I mentioned
some issues I had with the Python RC validation Jenkins target
<https://ci-beam.apache.org/job/beam_PostRelease_Python_Candidate/>. It
seemed appropriate to shunt that rant list of grievances over here instead
of cluttering up the vote thread, since I've been using this thread more
for general progress updates.

Frankly, that Jenkins target is really unwieldy for RC validation. It took
me like 2 days to finally get a useful signal from it for a variety of
reasons, the big one being that the target takes over 4 hours to run from
end to end, and the quickstarts and mobile gaming examples are interspersed
with each other, despite the validation sheet separating them. So if I get
a failure and I try a fix, it takes an extremely long time to actually get
a signal on it. Plus, the whole thing runs sequentially, so if one test
fails, none of the subsequent tests run at all, which makes debugging even
more of a pain.

Finally, the mobile examples are all used with a persistent BQ table on
apache-beam-testing instead of creating and deleting temporary tables. This
means that the examples are used with already populated tables, which
messes with test results (we can't tell if the example failed to write to
the table since it's already populated), and it means that
apache-beam-testing has constantly growing BQ tables hogging up space.

I worked around those issues for this release, but I think this target is a
good candidate to be refactored for future release managers (along with a
bunch of other little pain points I've been writing down). It shouldn't be
too hard to split it into two Jenkins targets, one for the quickstarts and
one for the mobile game examples, to adjust it so that processing continues
even if there's one failure, and to adjust it so that it generates
temporary BQ tables and deletes them once it's done.

I think I can figure those changes out myself, but if anyone has expertise
working with these tests and can find the time to help out (or make
the changes yourself), I would really appreciate it. While I can manage it,
it would probably get done faster and with better quality by someone who's
already familiar with these tests.

On Mon, Aug 31, 2020 at 10:25 PM Daniel Oliveira <da...@google.com>
wrote:

> The first release candidate is out. It took longer than I expected thanks
> to running into a few bits of user-unfriendliness, but mostly bugs due to
> me accidentally using JDK 11 with Gradle instead of JDK 8. I'm writing that
> down (along with all the other little difficulties I ran into) to make
> improvements to the release guide for the next release manager.
>
> Anyway, I sent out a thread for voting on the RC, so any issues with it
> can be mentioned in that thread. I just wanted to use this one as a
> progress report on my release experience, in case anyone is wondering what
> caused the release candidate to take so long.
>
> On Wed, Aug 12, 2020 at 6:09 PM Daniel Oliveira <da...@google.com>
> wrote:
>
>> 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 <da...@google.com>
>> 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 <da...@google.com>
>>> 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 <ru...@google.com> wrote:
>>>>
>>>>> Awesome!
>>>>>
>>>>>
>>>>> -Rui
>>>>>
>>>>> On Thu, Aug 6, 2020 at 4:14 PM Ahmet Altay <al...@google.com> wrote:
>>>>>
>>>>>> +1 - Thank you Daniel!!
>>>>>>
>>>>>> On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <
>>>>>> danoliveira@google.com> 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 <
>>>>>>> valentyn@google.com> wrote:
>>>>>>>
>>>>>>>> +1, Thanks Daniel!
>>>>>>>>
>>>>>>>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira <
>>>>>>>> danoliveira@google.com> 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
>>>>>>>>
>>>>>>>

Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Daniel Oliveira <da...@google.com>]

The first release candidate is out. It took longer than I expected thanks
to running into a few bits of user-unfriendliness, but mostly bugs due to
me accidentally using JDK 11 with Gradle instead of JDK 8. I'm writing that
down (along with all the other little difficulties I ran into) to make
improvements to the release guide for the next release manager.

Anyway, I sent out a thread for voting on the RC, so any issues with it can
be mentioned in that thread. I just wanted to use this one as a progress
report on my release experience, in case anyone is wondering what caused
the release candidate to take so long.

On Wed, Aug 12, 2020 at 6:09 PM Daniel Oliveira <da...@google.com>
wrote:

> 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 <da...@google.com>
> 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 <da...@google.com>
>> 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 <ru...@google.com> wrote:
>>>
>>>> Awesome!
>>>>
>>>>
>>>> -Rui
>>>>
>>>> On Thu, Aug 6, 2020 at 4:14 PM Ahmet Altay <al...@google.com> wrote:
>>>>
>>>>> +1 - Thank you Daniel!!
>>>>>
>>>>> On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <
>>>>> danoliveira@google.com> 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 <
>>>>>> valentyn@google.com> wrote:
>>>>>>
>>>>>>> +1, Thanks Daniel!
>>>>>>>
>>>>>>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira <
>>>>>>> danoliveira@google.com> 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
>>>>>>>
>>>>>>

Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Daniel Oliveira <da...@google.com>]

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 <da...@google.com>
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 <da...@google.com>
> 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 <ru...@google.com> wrote:
>>
>>> Awesome!
>>>
>>>
>>> -Rui
>>>
>>> On Thu, Aug 6, 2020 at 4:14 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> +1 - Thank you Daniel!!
>>>>
>>>> On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <da...@google.com>
>>>> 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 <
>>>>> valentyn@google.com> wrote:
>>>>>
>>>>>> +1, Thanks Daniel!
>>>>>>
>>>>>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira <
>>>>>> danoliveira@google.com> 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
>>>>>>
>>>>>

Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Daniel Oliveira <da...@google.com>]

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 <da...@google.com>
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 <ru...@google.com> wrote:
>
>> Awesome!
>>
>>
>> -Rui
>>
>> On Thu, Aug 6, 2020 at 4:14 PM Ahmet Altay <al...@google.com> wrote:
>>
>>> +1 - Thank you Daniel!!
>>>
>>> On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <da...@google.com>
>>> 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 <
>>>> valentyn@google.com> wrote:
>>>>
>>>>> +1, Thanks Daniel!
>>>>>
>>>>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira <
>>>>> danoliveira@google.com> 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
>>>>>
>>>>

Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Daniel Oliveira <da...@google.com>]

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 <ru...@google.com> wrote:

> Awesome!
>
>
> -Rui
>
> On Thu, Aug 6, 2020 at 4:14 PM Ahmet Altay <al...@google.com> wrote:
>
>> +1 - Thank you Daniel!!
>>
>> On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <da...@google.com>
>> 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 <va...@google.com>
>>> wrote:
>>>
>>>> +1, Thanks Daniel!
>>>>
>>>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira <da...@google.com>
>>>> 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
>>>>
>>>

Re: [PROPOSAL] Preparing for Beam 2.24.0 release

[Rui Wang <ru...@google.com>]

Awesome!


-Rui

On Thu, Aug 6, 2020 at 4:14 PM Ahmet Altay <al...@google.com> wrote:

> +1 - Thank you Daniel!!
>
> On Wed, Jul 29, 2020 at 4:30 PM Daniel Oliveira <da...@google.com>
> 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 <va...@google.com>
>> wrote:
>>
>>> +1, Thanks Daniel!
>>>
>>> On Wed, Jul 29, 2020 at 4:04 PM Daniel Oliveira <da...@google.com>
>>> 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
>>>
>>