[
https://issues.apache.org/jira/browse/BEAM-6441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17137415#comment-17137415
]
Beam JIRA Bot commented on BEAM-6441:
-------------------------------------
This issue was marked "stale-P2" and has not received a public comment in 14
days. It is now automatically moved to P3. If you are still affected by it, you
can comment and move it back to P2.
> cut_release_branch.sh should not push to master without verification and a PR
> -----------------------------------------------------------------------------
>
> Key: BEAM-6441
> URL: https://issues.apache.org/jira/browse/BEAM-6441
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Kenneth Knowles
> Priority: P3
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> Currently, the cut_release_branch.sh does many things:
> - Edits files in place to update the version
> - Makes a local commit
> - Pushing the local commit to master
> - Creates a new branch
> - Edits files in place to update the version
> - Pushes the release branch
> I think all of this except the push to master are OK. It is possible that we
> have something - website, examples, new places where the version is
> hardcoded, etc, that get broken in this process. Moving from x-SNAPSHOT to
> (x+1)-SNAPSHOT is easy to do in a pull request and safe. The release branch
> creation does not need to be synchronized with this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
