You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Jack McCluskey via dev <de...@beam.apache.org> on 2023/03/22 15:38:37 UTC
[PROPOSAL] Preparing for 2.47.0 Release
Hey all,
The next (2.47.0) release branch cut is scheduled for April 5th, 2023,
according to
the release calendar [1].
I will be performing this release. My plan is to cut the branch on that
date, and cherrypick release-blocking fixes afterwards, if any.
Please help me make sure the release goes smoothly by:
- Making sure that any unresolved release blocking issues for 2.47.0 should
have their "Milestone" marked as "2.47.0 Release" as soon as possible.
- Reviewing the current release blockers [2] and remove the Milestone if
they don't meet the criteria at [3].
Let me know if you have any comments/objections/questions.
Thanks,
Jack McCluskey
[1]
https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
[2] https://github.com/apache/beam/milestone/10
[3] https://beam.apache.org/contribute/release-blocking/
--
Jack McCluskey
SWE - DataPLS PLAT/ Dataflow ML
RDU
jrmccluskey@google.com
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Ahmed Abualsaud via dev <de...@beam.apache.org>.
Thanks for stepping up Jack!
On Thu, Mar 23, 2023 at 12:43 PM Ahmet Altay via dev <de...@beam.apache.org>
wrote:
> Thank you Jack!
>
> On Wed, Mar 22, 2023 at 8:39 AM Jack McCluskey via dev <
> dev@beam.apache.org> wrote:
>
>> Hey all,
>>
>> The next (2.47.0) release branch cut is scheduled for April 5th, 2023,
>> according to
>> the release calendar [1].
>>
>> I will be performing this release. My plan is to cut the branch on that
>> date, and cherrypick release-blocking fixes afterwards, if any.
>>
>> Please help me make sure the release goes smoothly by:
>> - Making sure that any unresolved release blocking issues
>> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release" as
>> soon as possible.
>> - Reviewing the current release blockers [2] and remove the Milestone if
>> they don't meet the criteria at [3].
>>
>> Let me know if you have any comments/objections/questions.
>>
>> Thanks,
>>
>> Jack McCluskey
>>
>> [1]
>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>> [2] https://github.com/apache/beam/milestone/10
>> [3] https://beam.apache.org/contribute/release-blocking/
>>
>> --
>>
>>
>> Jack McCluskey
>> SWE - DataPLS PLAT/ Dataflow ML
>> RDU
>> jrmccluskey@google.com
>>
>>
>>
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Ahmet Altay via dev <de...@beam.apache.org>.
Thank you Jack!
On Wed, Mar 22, 2023 at 8:39 AM Jack McCluskey via dev <de...@beam.apache.org>
wrote:
> Hey all,
>
> The next (2.47.0) release branch cut is scheduled for April 5th, 2023,
> according to
> the release calendar [1].
>
> I will be performing this release. My plan is to cut the branch on that
> date, and cherrypick release-blocking fixes afterwards, if any.
>
> Please help me make sure the release goes smoothly by:
> - Making sure that any unresolved release blocking issues
> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release" as
> soon as possible.
> - Reviewing the current release blockers [2] and remove the Milestone if
> they don't meet the criteria at [3].
>
> Let me know if you have any comments/objections/questions.
>
> Thanks,
>
> Jack McCluskey
>
> [1]
> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
> [2] https://github.com/apache/beam/milestone/10
> [3] https://beam.apache.org/contribute/release-blocking/
>
> --
>
>
> Jack McCluskey
> SWE - DataPLS PLAT/ Dataflow ML
> RDU
> jrmccluskey@google.com
>
>
>
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Ahmet Altay via dev <de...@beam.apache.org>.
Thank you for the update Jack!
On Tue, Apr 18, 2023 at 11:23 AM Jack McCluskey <jr...@google.com>
wrote:
> Quick update for everyone, the initial release blockers on the 2.47.0
> milestone have been resolved and the RC1 commit has been tagged. I'll be
> working on getting RC1 artifacts built now.
>
> On Thu, Apr 13, 2023 at 12:22 PM Ahmet Altay <al...@google.com> wrote:
>
>> Sounds good. Thank you. And if you need help please reach out.
>>
>> On Thu, Apr 13, 2023 at 6:29 AM Jack McCluskey <jr...@google.com>
>> wrote:
>>
>>> We're making good progress on finding and fixing bugs. Not quite to
>>> building an RC candidate yet, but so far nothing that seems to be a
>>> difficult fix.
>>>
>>> On Wed, Apr 12, 2023 at 8:10 PM Ahmet Altay <al...@google.com> wrote:
>>>
>>>> Jack, how is the release coming along?
>>>>
>>>> On Tue, Apr 4, 2023 at 12:23 PM Jack McCluskey via dev <
>>>> dev@beam.apache.org> wrote:
>>>>
>>>>> Hey everyone,
>>>>>
>>>>> I need a PMC member's help adding my pubkey to
>>>>> https://dist.apache.org/repos/dist/release/beam/KEYS as well as
>>>>> adding PyPI user jrmccluskey to the maintainers of the Apache Beam package.
>>>>> These are the last steps I have to do to complete prep for the release.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jack McCluskey
>>>>>
>>>>> On Wed, Mar 22, 2023 at 11:38 AM Jack McCluskey <
>>>>> jrmccluskey@google.com> wrote:
>>>>>
>>>>>> Hey all,
>>>>>>
>>>>>> The next (2.47.0) release branch cut is scheduled for April 5th,
>>>>>> 2023, according to
>>>>>> the release calendar [1].
>>>>>>
>>>>>> I will be performing this release. My plan is to cut the branch on
>>>>>> that date, and cherrypick release-blocking fixes afterwards, if any.
>>>>>>
>>>>>> Please help me make sure the release goes smoothly by:
>>>>>> - Making sure that any unresolved release blocking issues
>>>>>> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release"
>>>>>> as soon as possible.
>>>>>> - Reviewing the current release blockers [2] and remove the
>>>>>> Milestone if they don't meet the criteria at [3].
>>>>>>
>>>>>> Let me know if you have any comments/objections/questions.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Jack McCluskey
>>>>>>
>>>>>> [1]
>>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>>> [2] https://github.com/apache/beam/milestone/10
>>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>>
>>>>>> --
>>>>>>
>>>>>>
>>>>>> Jack McCluskey
>>>>>> SWE - DataPLS PLAT/ Dataflow ML
>>>>>> RDU
>>>>>> jrmccluskey@google.com
>>>>>>
>>>>>>
>>>>>>
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Jack McCluskey via dev <de...@beam.apache.org>.
Quick update for everyone, the initial release blockers on the 2.47.0
milestone have been resolved and the RC1 commit has been tagged. I'll be
working on getting RC1 artifacts built now.
On Thu, Apr 13, 2023 at 12:22 PM Ahmet Altay <al...@google.com> wrote:
> Sounds good. Thank you. And if you need help please reach out.
>
> On Thu, Apr 13, 2023 at 6:29 AM Jack McCluskey <jr...@google.com>
> wrote:
>
>> We're making good progress on finding and fixing bugs. Not quite to
>> building an RC candidate yet, but so far nothing that seems to be a
>> difficult fix.
>>
>> On Wed, Apr 12, 2023 at 8:10 PM Ahmet Altay <al...@google.com> wrote:
>>
>>> Jack, how is the release coming along?
>>>
>>> On Tue, Apr 4, 2023 at 12:23 PM Jack McCluskey via dev <
>>> dev@beam.apache.org> wrote:
>>>
>>>> Hey everyone,
>>>>
>>>> I need a PMC member's help adding my pubkey to
>>>> https://dist.apache.org/repos/dist/release/beam/KEYS as well as adding
>>>> PyPI user jrmccluskey to the maintainers of the Apache Beam package. These
>>>> are the last steps I have to do to complete prep for the release.
>>>>
>>>> Thanks,
>>>>
>>>> Jack McCluskey
>>>>
>>>> On Wed, Mar 22, 2023 at 11:38 AM Jack McCluskey <jr...@google.com>
>>>> wrote:
>>>>
>>>>> Hey all,
>>>>>
>>>>> The next (2.47.0) release branch cut is scheduled for April 5th,
>>>>> 2023, according to
>>>>> the release calendar [1].
>>>>>
>>>>> I will be performing this release. My plan is to cut the branch on
>>>>> that date, and cherrypick release-blocking fixes afterwards, if any.
>>>>>
>>>>> Please help me make sure the release goes smoothly by:
>>>>> - Making sure that any unresolved release blocking issues
>>>>> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release"
>>>>> as soon as possible.
>>>>> - Reviewing the current release blockers [2] and remove the Milestone
>>>>> if they don't meet the criteria at [3].
>>>>>
>>>>> Let me know if you have any comments/objections/questions.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Jack McCluskey
>>>>>
>>>>> [1]
>>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>>> [2] https://github.com/apache/beam/milestone/10
>>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> Jack McCluskey
>>>>> SWE - DataPLS PLAT/ Dataflow ML
>>>>> RDU
>>>>> jrmccluskey@google.com
>>>>>
>>>>>
>>>>>
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Ahmet Altay via dev <de...@beam.apache.org>.
Sounds good. Thank you. And if you need help please reach out.
On Thu, Apr 13, 2023 at 6:29 AM Jack McCluskey <jr...@google.com>
wrote:
> We're making good progress on finding and fixing bugs. Not quite to
> building an RC candidate yet, but so far nothing that seems to be a
> difficult fix.
>
> On Wed, Apr 12, 2023 at 8:10 PM Ahmet Altay <al...@google.com> wrote:
>
>> Jack, how is the release coming along?
>>
>> On Tue, Apr 4, 2023 at 12:23 PM Jack McCluskey via dev <
>> dev@beam.apache.org> wrote:
>>
>>> Hey everyone,
>>>
>>> I need a PMC member's help adding my pubkey to
>>> https://dist.apache.org/repos/dist/release/beam/KEYS as well as adding
>>> PyPI user jrmccluskey to the maintainers of the Apache Beam package. These
>>> are the last steps I have to do to complete prep for the release.
>>>
>>> Thanks,
>>>
>>> Jack McCluskey
>>>
>>> On Wed, Mar 22, 2023 at 11:38 AM Jack McCluskey <jr...@google.com>
>>> wrote:
>>>
>>>> Hey all,
>>>>
>>>> The next (2.47.0) release branch cut is scheduled for April 5th, 2023,
>>>> according to
>>>> the release calendar [1].
>>>>
>>>> I will be performing this release. My plan is to cut the branch on that
>>>> date, and cherrypick release-blocking fixes afterwards, if any.
>>>>
>>>> Please help me make sure the release goes smoothly by:
>>>> - Making sure that any unresolved release blocking issues
>>>> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release" as
>>>> soon as possible.
>>>> - Reviewing the current release blockers [2] and remove the Milestone
>>>> if they don't meet the criteria at [3].
>>>>
>>>> Let me know if you have any comments/objections/questions.
>>>>
>>>> Thanks,
>>>>
>>>> Jack McCluskey
>>>>
>>>> [1]
>>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>>> [2] https://github.com/apache/beam/milestone/10
>>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>>
>>>> --
>>>>
>>>>
>>>> Jack McCluskey
>>>> SWE - DataPLS PLAT/ Dataflow ML
>>>> RDU
>>>> jrmccluskey@google.com
>>>>
>>>>
>>>>
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Jack McCluskey via dev <de...@beam.apache.org>.
We're making good progress on finding and fixing bugs. Not quite to
building an RC candidate yet, but so far nothing that seems to be a
difficult fix.
On Wed, Apr 12, 2023 at 8:10 PM Ahmet Altay <al...@google.com> wrote:
> Jack, how is the release coming along?
>
> On Tue, Apr 4, 2023 at 12:23 PM Jack McCluskey via dev <
> dev@beam.apache.org> wrote:
>
>> Hey everyone,
>>
>> I need a PMC member's help adding my pubkey to
>> https://dist.apache.org/repos/dist/release/beam/KEYS as well as adding
>> PyPI user jrmccluskey to the maintainers of the Apache Beam package. These
>> are the last steps I have to do to complete prep for the release.
>>
>> Thanks,
>>
>> Jack McCluskey
>>
>> On Wed, Mar 22, 2023 at 11:38 AM Jack McCluskey <jr...@google.com>
>> wrote:
>>
>>> Hey all,
>>>
>>> The next (2.47.0) release branch cut is scheduled for April 5th, 2023,
>>> according to
>>> the release calendar [1].
>>>
>>> I will be performing this release. My plan is to cut the branch on that
>>> date, and cherrypick release-blocking fixes afterwards, if any.
>>>
>>> Please help me make sure the release goes smoothly by:
>>> - Making sure that any unresolved release blocking issues
>>> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release" as
>>> soon as possible.
>>> - Reviewing the current release blockers [2] and remove the Milestone
>>> if they don't meet the criteria at [3].
>>>
>>> Let me know if you have any comments/objections/questions.
>>>
>>> Thanks,
>>>
>>> Jack McCluskey
>>>
>>> [1]
>>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>>> [2] https://github.com/apache/beam/milestone/10
>>> [3] https://beam.apache.org/contribute/release-blocking/
>>>
>>> --
>>>
>>>
>>> Jack McCluskey
>>> SWE - DataPLS PLAT/ Dataflow ML
>>> RDU
>>> jrmccluskey@google.com
>>>
>>>
>>>
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Ahmet Altay via dev <de...@beam.apache.org>.
Jack, how is the release coming along?
On Tue, Apr 4, 2023 at 12:23 PM Jack McCluskey via dev <de...@beam.apache.org>
wrote:
> Hey everyone,
>
> I need a PMC member's help adding my pubkey to
> https://dist.apache.org/repos/dist/release/beam/KEYS as well as adding
> PyPI user jrmccluskey to the maintainers of the Apache Beam package. These
> are the last steps I have to do to complete prep for the release.
>
> Thanks,
>
> Jack McCluskey
>
> On Wed, Mar 22, 2023 at 11:38 AM Jack McCluskey <jr...@google.com>
> wrote:
>
>> Hey all,
>>
>> The next (2.47.0) release branch cut is scheduled for April 5th, 2023,
>> according to
>> the release calendar [1].
>>
>> I will be performing this release. My plan is to cut the branch on that
>> date, and cherrypick release-blocking fixes afterwards, if any.
>>
>> Please help me make sure the release goes smoothly by:
>> - Making sure that any unresolved release blocking issues
>> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release" as
>> soon as possible.
>> - Reviewing the current release blockers [2] and remove the Milestone if
>> they don't meet the criteria at [3].
>>
>> Let me know if you have any comments/objections/questions.
>>
>> Thanks,
>>
>> Jack McCluskey
>>
>> [1]
>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>> [2] https://github.com/apache/beam/milestone/10
>> [3] https://beam.apache.org/contribute/release-blocking/
>>
>> --
>>
>>
>> Jack McCluskey
>> SWE - DataPLS PLAT/ Dataflow ML
>> RDU
>> jrmccluskey@google.com
>>
>>
>>
Re: [PROPOSAL] Preparing for 2.47.0 Release
Posted by Jack McCluskey via dev <de...@beam.apache.org>.
Hey everyone,
I need a PMC member's help adding my pubkey to
https://dist.apache.org/repos/dist/release/beam/KEYS as well as adding PyPI
user jrmccluskey to the maintainers of the Apache Beam package. These are
the last steps I have to do to complete prep for the release.
Thanks,
Jack McCluskey
On Wed, Mar 22, 2023 at 11:38 AM Jack McCluskey <jr...@google.com>
wrote:
> Hey all,
>
> The next (2.47.0) release branch cut is scheduled for April 5th, 2023,
> according to
> the release calendar [1].
>
> I will be performing this release. My plan is to cut the branch on that
> date, and cherrypick release-blocking fixes afterwards, if any.
>
> Please help me make sure the release goes smoothly by:
> - Making sure that any unresolved release blocking issues
> for 2.47.0 should have their "Milestone" marked as "2.47.0 Release" as
> soon as possible.
> - Reviewing the current release blockers [2] and remove the Milestone if
> they don't meet the criteria at [3].
>
> Let me know if you have any comments/objections/questions.
>
> Thanks,
>
> Jack McCluskey
>
> [1]
> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
> [2] https://github.com/apache/beam/milestone/10
> [3] https://beam.apache.org/contribute/release-blocking/
>
> --
>
>
> Jack McCluskey
> SWE - DataPLS PLAT/ Dataflow ML
> RDU
> jrmccluskey@google.com
>
>
>