[
https://issues.apache.org/jira/browse/BEAM-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341543#comment-16341543
]
Valentyn Tymofieiev commented on BEAM-3392:
-------------------------------------------
Yes, it's an action to perform on a branch. The intention for the Jira was to
do a one-time check for 2.3.0, and setting fix version to 2.3.0 meant that
someone will look into this.
I agree that a release verification spreadsheet is a cleaner way to track this.
Feel free to add an item to the spreadsheet and remove it from 2.3.0 blockers.
Also, we could add information about the spreadsheet to our release
documentation
https://beam.apache.org/contribute/release-guide/#vote-on-the-release-candidate.
> Verify default container image names in Python SDK
> --------------------------------------------------
>
> Key: BEAM-3392
> URL: https://issues.apache.org/jira/browse/BEAM-3392
> Project: Beam
> Issue Type: Test
> Components: runner-dataflow
> Affects Versions: 2.3.0
> Reporter: Valentyn Tymofieiev
> Assignee: Valentyn Tymofieiev
> Priority: Blocker
> Fix For: 2.3.0
>
>
> Verify naming pattern for python containers in 2.3.0 release:
> - default legacy worker harness container image:
> dataflow.gcr.io/v1beta3/python:2.3.0
> - pinned runner harness container image: dataflow.gcr.io/v1beta3/harness:2.3.0
> - default SDK harness container name (portable pipelines): name may change,
> exact pattern TBD.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
