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 <jrmcclus...@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 > jrmcclus...@google.com > > >
