There are still extant issues [1] that need handling, so if you've seen a
comment from me on one of those issues, please respond if a cherry pick is
needed, or mark the issue as resolved.

So no RC has been cut at this time.

However, the nightly snapshot issue was resolved! [2]  Thank you!

This week was particularly heavy for me for unrelated reasons, so I haven't
been ushering the issues through as optimally as I can. See you next week.

Cheers,
Robert Burke
2.26 Release Manager

[1]  https://issues.apache.org/jira/projects/BEAM/versions/12348833
[2] https://issues.apache.org/jira/browse/BEAM-11214

On Mon, 9 Nov 2020 at 16:04, Robert Burke <[email protected]> wrote:

> Hello Beam Dev!
>
> The 2.26 branch has been cut [1] and is open for cherry pick requests.
> Current open issues [2] are presently minimal, and I'll be triaging them in
> earnest for inclusion into the release branch on Wednesday.
>
> There's presently an issue I can use help with with the current nightly
> snapshot [3] BEAM-11214 [4], and the cut verification [5] is pretty clean
> with only one outstanding test suite failure WRT Python 3.7 on
> windows BEAM-11209 [6].
>
> If there are any Java or Python experts in the house, I would appreciate
> their assistance with those issues ([4][6]), as I am but a humble Go
> developer, who now has several versions of each language installed on his
> machine and is confused by all of them.
>
> If there are no cherry pick requests for issues that remain in triage by
> Thursday November 12th, I will cut an initial release candidate. Either
> way, I'll send another update on that day with the current state of the
> release.
>
> Cheers,
> Robert Burke
> 2.26 Release Manager
>
> [1] https://github.com/apache/beam/tree/release-2.26.0
> [2] https://issues.apache.org/jira/projects/BEAM/versions/12348833
> [3] https://github.com/apache/beam/pull/13274
> [4] https://issues.apache.org/jira/browse/BEAM-11214
> [5] https://github.com/apache/beam/pull/13275
> [6] https://issues.apache.org/jira/browse/BEAM-11209
>

Reply via email to