Re: [PROPOSAL] Preparing for 2.48.0 Release

2023-05-17 Thread Ritesh Ghorse via dev
I'm waiting for these last 4 issues ( https://github.com/apache/beam/milestone/12) which have associated PRs to get merged and I'll cut the branch after that. On Wed, May 17, 2023 at 12:23 PM Ritesh Ghorse wrote: > To get the release going, > Could a PMC member help me by adding my key to > http

Re: [PROPOSAL] Preparing for 2.48.0 Release

2023-05-17 Thread Ritesh Ghorse via dev
To get the release going, Could a PMC member help me by adding my key to https://dist.apache.org/repos/dist/release/beam/KEYS? I've appended my key to https://dist.apache.org/repos/dist/dev/beam/KEYS. Also, could someone please add me (username: riteshghorse) to the maintainers group at https://p

Re: Repository Deletion Postmortem

2023-05-17 Thread Alexey Romanenko
Thanks for follow-up on this, it should be helpful. > The git revert command was used to create a revert commit. However, the > created commit deleted the entire repository. Do you have an idea what was a command and how it could deleted the entire repository? I’m asking about this to find a p

Beam High Priority Issue Report (34)

2023-05-17 Thread beamactions
This is your daily summary of Beam's current high priority issues that may need attention. See https://beam.apache.org/contribute/issue-priorities for the meaning and expectations around issue priorities. Unassigned P1 Issues: https://github.com/apache/beam/issues/26723 [Failing Test]: Tou