Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/4407#discussion_r129824175
--- Diff: pom.xml ---
@@ -1257,6 +1243,17 @@ under the License.
<pluginManagement>
<plugins>
+ <plugin>
+
<groupId>org.apache.maven.plugins</groupId>
+
<artifactId>maven-release-plugin</artifactId>
--- End diff --
We were actually not using this before, it was just a leftover in there.
It's not even required for our release process, i.e. in the release profile.
However, the plugin can be used to do the stuff that we do in scripts and
manually. For example , I can do
```
mvn release:branch \
-DbranchName=${BRANCH_NAME} \
-DdevelopmentVersion=${DEVELOPMENT_VERSION}
```
to update the version on master and fork of the branch for a newly released
version.
Then I could use
```
mvn release:prepare \
-Dresume=false \
-DreleaseVersion=${VERSION} \
-Dtag=${TAG} \
-DupdateWorkingCopyVersions=false
```
and
```
mvn release:perform
```
to build the actual release, create the source release, upload the (signed)
jars to sonatype and create the release tag.
(I was experimenting with this when preparing for the next release and our
release infrastructure is very _interesting_.)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
