[
https://issues.apache.org/jira/browse/BEAM-6441?focusedWorklogId=224620&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-224620
]
ASF GitHub Bot logged work on BEAM-6441:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Apr/19 21:53
Start Date: 08/Apr/19 21:53
Worklog Time Spent: 10m
Work Description: apilloud commented on pull request #8223: [BEAM-6441]
Revise release branch cut instructions
URL: https://github.com/apache/beam/pull/8223#discussion_r273254159
##########
File path: website/src/contribute/release-guide.md
##########
@@ -1025,7 +1010,8 @@ Merge the website pull request to [list the release]({{
site.baseurl }}/get-star
### Mark the version as released in JIRA
-In JIRA, inside [version
management](https://issues.apache.org/jira/plugins/servlet/project-config/BEAM/versions),
hover over the current release and a settings menu will appear. Click
`Release`, and select today’s date.
+Navigate to the [list of releases in
Jira](https://issues.apache.org/jira/projects/BEAM/releases) and select the one
you
+are finalizing. In the upper left, click the "Release" button.
Review comment:
This UI doesn't exist for me, so I assume this is another place you need to
be a JIRA admin?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 224620)
Time Spent: 50m (was: 40m)
> 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: Bug
> Components: build-system
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Major
> Labels: triaged
> Time Spent: 50m
> 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
(v7.6.3#76005)
