2.47.0 Release Update and Brief Code Freeze

[Jack McCluskey via dev <de...@beam.apache.org>]

Hey everyone,

While I was working on cutting the release branch this afternoon I hit a
snag with the release script, and in trying to revert the halfway-completed
work on that the entire Beam repo was (briefly)
deleted. This has been fixed, but as a consequence of this and the
permissions on the repo the history for the repo is messed up (AKA every
file has a removal and restoration in its history now.) While we work with
infra to gain permission to amend the history (tracking for that will be at
https://issues.apache.org/jira/browse/INFRA-24433) we will have a brief
code freeze to ensure that everything is restored properly.

I take full responsibility for the incident and will be working on
diagnosing how this happened + improving the release process so this can't
happen again.

Thanks,

Jack McCluskey
-- 


Jack McCluskey
SWE - DataPLS PLAT/ Dataflow ML
RDU
jrmccluskey@google.com

Re: 2.47.0 Release Update and Brief Code Freeze

[Kerry Donny-Clark via dev <de...@beam.apache.org>]

Thanks for the transparent and quick explanation! Identifying an issue,
taking steps to correct it, and documenting what went wrong is exactly how
we should address isssues like this.
Kerry

On Wed, Apr 5, 2023, 4:53 PM Jack McCluskey via dev <de...@beam.apache.org>
wrote:

> Hey everyone,
>
> While I was working on cutting the release branch this afternoon I hit a
> snag with the release script, and in trying to revert the halfway-completed
> work on that the entire Beam repo was (briefly)
> deleted. This has been fixed, but as a consequence of this and the
> permissions on the repo the history for the repo is messed up (AKA every
> file has a removal and restoration in its history now.) While we work with
> infra to gain permission to amend the history (tracking for that will be at
> https://issues.apache.org/jira/browse/INFRA-24433) we will have a brief
> code freeze to ensure that everything is restored properly.
>
> I take full responsibility for the incident and will be working on
> diagnosing how this happened + improving the release process so this can't
> happen again.
>
> Thanks,
>
> Jack McCluskey
> --
>
>
> Jack McCluskey
> SWE - DataPLS PLAT/ Dataflow ML
> RDU
> jrmccluskey@google.com
>
>
>

Re: 2.47.0 Release Update and Brief Code Freeze

[Jack McCluskey via dev <de...@beam.apache.org>]

Hey folks,

Thank you for your patience and understanding. The repo has been returned
to a good state and the code freeze has been lifted. I'll be *actually* cutting
the release branch shortly.

Thanks,

Jack McCluskey

On Wed, Apr 5, 2023 at 4:52 PM Jack McCluskey <jr...@google.com>
wrote:

> Hey everyone,
>
> While I was working on cutting the release branch this afternoon I hit a
> snag with the release script, and in trying to revert the halfway-completed
> work on that the entire Beam repo was (briefly)
> deleted. This has been fixed, but as a consequence of this and the
> permissions on the repo the history for the repo is messed up (AKA every
> file has a removal and restoration in its history now.) While we work with
> infra to gain permission to amend the history (tracking for that will be at
> https://issues.apache.org/jira/browse/INFRA-24433) we will have a brief
> code freeze to ensure that everything is restored properly.
>
> I take full responsibility for the incident and will be working on
> diagnosing how this happened + improving the release process so this can't
> happen again.
>
> Thanks,
>
> Jack McCluskey
> --
>
>
> Jack McCluskey
> SWE - DataPLS PLAT/ Dataflow ML
> RDU
> jrmccluskey@google.com
>
>
>