[
https://issues.apache.org/jira/browse/BEAM-3255?focusedWorklogId=93204&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-93204
]
ASF GitHub Bot logged work on BEAM-3255:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Apr/18 13:37
Start Date: 20/Apr/18 13:37
Worklog Time Spent: 10m
Work Description: alanmyrvold commented on a change in pull request #424:
[BEAM-3255] Updating release guide to use Gradle commands
URL: https://github.com/apache/beam-site/pull/424#discussion_r183043380
##########
File path: src/contribute/release-guide.md
##########
@@ -189,30 +189,35 @@ Check out the version of the codebase from which you
start the release. For a ne
Set up a few environment variables to simplify Maven commands that follow. (We
use `bash` Unix syntax in this guide.)
- VERSION="1.2.3"
- NEXT_VERSION="1.2.4"
- BRANCH_NAME="release-${VERSION}"
- DEVELOPMENT_VERSION="${NEXT_VERSION}-SNAPSHOT"
+ RELEASE_VERSION=2.5.0
+ NEXT_VERSION_IN_BASE_BRANCH=2.6.0
+ BRANCH=release-${RELEASE}
Version represents the release currently underway, while next version
specifies the anticipated next version to be released from that branch.
Normally, 1.2.0 is followed by 1.3.0, while 1.2.3 is followed by 1.2.4.
-Use Maven release plugin to create the release branch and update the current
branch to use the new development version. This command applies for the new
major or minor version. (Warning: this command automatically pushes changes to
the code repository.)
+**NOTE**: Only if you are doing an incremental/hotfix releasei (e.g. 2.5.1),
please check out the previous release tag, before running the following
instructions:
- mvn release:branch \
- -DbranchName=${BRANCH_NAME} \
- -DdevelopmentVersion=${DEVELOPMENT_VERSION}
+ BASE_RELEASE=2.5.0
+ RELEASE=2.5.1
+ NEXT_VERSION_IN_BASE_BRANCH=2.5.0
+ git checkout tags/${BASE_RELEASE}
-However, if you are doing an incremental/hotfix release, please run the
following command after checking out the release tag of the release being
patched.
+Create a new branch, and update version files in the master branch.
- mvn release:branch \
- -DbranchName=${BRANCH_NAME} \
- -DupdateWorkingCopyVersions=false \
- -DupdateBranchVersions=true \
- -DreleaseVersion="${VERSION}-SNAPSHOT"
+ git branch ${BRANCH}
Review comment:
Do we need to clarify that the branch is to made on the upstream apache/beam
repo and pushed, and not on a fork, or is something done by the release plugin?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 93204)
Time Spent: 3h 20m (was: 3h 10m)
> Update release process to use Gradle
> ------------------------------------
>
> Key: BEAM-3255
> URL: https://issues.apache.org/jira/browse/BEAM-3255
> Project: Beam
> Issue Type: Sub-task
> Components: build-system
> Reporter: Luke Cwik
> Assignee: Alan Myrvold
> Priority: Major
> Fix For: Not applicable
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> This task is about configuring Gradle to generate pom's and artifacts
> required to perform a release and update the nightly release snapshot Jenkins
> jobs found here
> https://github.com/apache/beam/blob/master/.test-infra/jenkins/job_beam_Release_NightlySnapshot.groovy
> We will also require some integration tests to run against the released
> nightly snapshot artifacts to ensure that what was built is valid.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
