On Mon, May 25, 2020 at 1:30 PM Steve Niemitz <[email protected]> wrote:
> I tried to validate the release branch on dataflow, but it looks like > there's no tag yet for the 2.22 docker containers [1] > I haven't built any Dataflow containers yet since BEAM-9971 and BEAM-10057 are actively being worked on and their PRs will be cherry-picked into the release branch. > I'm also fairly concerned with the artifact staging regressions introduced > in BEAM-9383 [2] > There are some Jiras related to artifact staging that are currently marked as release blockers: BEAM-10077, BEAM-10078. I didn't initially see the connection to a regression, but based on your comments it sounds like those should in fact be release blockers. > > [1] > https://console.cloud.google.com/gcr/images/cloud-dataflow/GLOBAL/v1beta3/beam-java-streaming?gcrImageListsize=30&gcrImageListquery=%255B%255D > [2] > https://issues.apache.org/jira/browse/BEAM-9383?focusedCommentId=17116185&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17116185 > > On Wed, May 20, 2020 at 10:10 PM Brian Hulette <[email protected]> > wrote: > >> Hi everyone, >> >> It's time for dueling release branches! The 2.22.0 branch has been cut >> [1]. >> - If you notice any release blockers [2] please tag a jira with fix >> version 2.22.0 and cc me (bhulette). >> - Please update the change log [3] with any significant changes if you >> haven't yet. Put up a PR with the change and tag me (@TheNeuralBit on >> github). >> >> Thanks! >> Brian >> >> >> [1] https://github.com/apache/beam/tree/release-2.22.0 >> [2] https://beam.apache.org/contribute/release-blocking/ >> [3] https://github.com/apache/beam/blob/master/CHANGES.md >> >
