There are some test failures on the release branch that need to be addressed.I may need help with a Samza ValidatesRunner failure . It has been failing since at least June 24 .1. Did this issue come up during earlier releases?2. Do we know why this suite is not visible in Beam metrics dashboard? If it was, it would have been easier to see when it started failing.Can Samza runner maintainers please advise?Thank you.On Tue, Jul 7, 2020 at 8:01 PM Valentyn Tymofieiev <email@example.com> wrote:So far the release process is going well.Currently running several release validation suites, and plan to send out an RC once these are completed.Here is how the community can help:1. If there is a test suite that you've added recently, but did not add it to .test-infra/jenkins/README.md, feel free to trigger it on the PR, and add the trigger command to README.MD.2. Please add any noteworthy changes to the change log .3. I have received several inquiries off-the-list about cherry-picking changes to the release branch (which would be blocking further steps in the release process), so I would like to remind the current guideline: An issue should not block the release if the problem exists in the current released version or is a bug in new functionality that does not exist in the current released version. It should be a blocker if the bug is a regression between the currently released version and the release in progress and has no easy workaround.Thanks,ValentynOn Mon, Jul 6, 2020 at 9:47 AM Ahmet Altay <firstname.lastname@example.org> wrote:Done.On Wed, Jul 1, 2020 at 5:40 PM Valentyn Tymofieiev <email@example.com> wrote:Can somebody please add my pypi username (tvalentyn) to the list of apache-beam maintainers on PyPi: https://pypi.org/project/apache-beam/ ?Thank you!On Wed, Jul 1, 2020 at 4:51 PM Valentyn Tymofieiev <firstname.lastname@example.org> wrote:Release branch has been cut.As a reminder, please do not merge commits into the release branch directly, instead, loop in the release manager if any cherry-picks are required.Thank you.On Wed, Jul 1, 2020 at 9:25 AM Valentyn Tymofieiev <email@example.com> wrote:Great, thank you Tobiasz, I will take a look.On Wed, Jul 1, 2020 at 7:27 AM Tobiasz Kędzierski <firstname.lastname@example.org> wrote:Hi,
I've just created PR introducing usage of GH-Actions to release process
Let me know what you think, maybe you have some suggestions on what may be improved.
TobiaszOn Wed, Jul 1, 2020 at 6:08 AM Ahmet Altay <email@example.com> wrote:Valentyn,+firstname.lastname@example.org added a github action for building python wheel files (https://github.com/apache/beam/pull/11877). You should be able to build the wheel files using this github action instead of using the beam-wheels repo and Travis. Please give it a try during the release process.AhmetOn Tue, Jun 23, 2020 at 7:27 PM Valentyn Tymofieiev <email@example.com> wrote:Friendly reminder that the release cut is slated next week.If you are aware of *release-blocking* issues, please open a JIRA and set the "Fix version" to be 2.23.0.Please do not set "Fix version" for open non-blocking issues, instead set "Fix version" once the issue is actually resolved.Thanks,ValentynOn Mon, Jun 15, 2020 at 1:14 PM Rui Wang <firstname.lastname@example.org> wrote:Thank you Valentyn!On Mon, Jun 15, 2020 at 1:08 PM Ahmet Altay <email@example.com> wrote:Thank you Valentyn!On Mon, Jun 15, 2020 at 12:46 PM Ankur Goenka <firstname.lastname@example.org> wrote:Thanks Valentyn!On Mon, Jun 15, 2020 at 12:41 PM Kyle Weaver <email@example.com> wrote:Sounds good, thanks Valentyn!On Mon, Jun 15, 2020 at 12:31 PM Valentyn Tymofieiev <firstname.lastname@example.org> wrote:Hi all,According to the Beam release calendar , the next (2.23.0) release branch cut is scheduled for July 1.I would be happy to help with this release and volunteer myself to be the next release manager.As usual, the plan is to cut the branch on that date, and cherrypick release-blocking fixes afterwards if any.Any unresolved release blocking JIRA issues for 2.23.0 should have their "Fix Version/s" marked as "2.23.0".Any comments or objections? https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com--