Update RELEASING

Author: mpkorstanje

Makefile

@@ -18,6 +18,14 @@ version:
 	@echo ""
 .PHONY: version
 
+update-compatibility:
+	MSG_VERSION=$$(mvn help:evaluate -Dexpression=messages.version -q -DforceStdout 2> /dev/null) && \
+	git clone --branch messages/v$$MSG_VERSION git@github.com:cucumber/cucumber.git target/cucumber
+	rm -rf compatibility/src/test/resources/*
+	cp -r target/cucumber/compatibility-kit/javascript/features compatibility/src/test/resources
+	rm -rf target/cucumber
+.PHONY: update-compatibility
+
 update-dependency-versions:
 	mvn versions:force-releases
 	mvn versions:update-properties -DallowMajorUpdates=false -Dmaven.version.rules="file://`pwd`/.m2/maven-version-rules.xml"
@@ -48,5 +56,6 @@ release: default update-changelog update-installdoc .commit-and-push-changelog-a
 	git checkout "v$(NEW_VERSION)"
 	mvn deploy -P-examples -P-compatibility -Psign-source-javadoc -DskipTests=true -DskipITs=true -Darchetype.test.skip=true
 	git checkout $(CURRENT_BRANCH)
+	git fetch
 .PHONY: release
 

RELEASING.md

@@ -1,46 +1,38 @@
 Releasing
 =========
 
-The process of deploying to maven central has been automated based on 
-the [Complete guide to continuous deployment to maven central from Travis CI](http://www.debonair.io/post/maven-cd/)
-and will be executed whenever a non-snapshot version is committed.
+The deployment process of `cucumber-jvm-scala` is based on 
+[Deploying to OSSRH with Apache Maven](http://central.sonatype.org/pages/apache-maven.html#deploying-to-ossrh-with-apache-maven-introduction).
 
-## Check [![Build Status](https://travis-ci.org/cucumber/cucumber-jvm-scala.svg?branch=main)](https://travis-ci.org/cucumber/cucumber-jvm-scala) ##
+## Check [![Build Status](https://travis-ci.org/cucumber/cucumber-jvm.svg?branch=main)](https://travis-ci.org/cucumber/cucumber-jvm) ##
 
 Is the build passing?
 
 ```
-git checkout master
+git checkout main
 ```
 
 Also check if you can upgrade any dependencies:
 
 ```
-mvn versions:display-dependency-updates
+make update-dependency-versions
 ```
 
 ## Make the release ##
 
-Now release everything:
+Remove the empty sections in the changelog. Don't commit these but run: 
 
 ```
-mvn release:clean release:prepare -DautoVersionSubmodules=true -Darguments="-DskipTests=true"  
+make version
 ```
 
-Travis will now deploy everything.
-
-It is preferable to use the automated deployment process over the manual process. However should travis.ci fail or should the 
-need arise to setup another continuous integration system the [Manual deployment](#manual-deployment) section 
-describes how this works.
-
-# Manual deployment #
+Check if branch name and version are as expected.
 
-It is preferable to use the automated deployment process over the manual process.
+```
+make release
+``` 
 
-The deployment process of `cucumber-jvm` is based on 
-[Deploying to OSSRH with Apache Maven](http://central.sonatype.org/pages/apache-maven.html#deploying-to-ossrh-with-apache-maven-introduction).
-This process is nearly identical for both snapshot deployments and releases. Whether a snapshot 
-deployment or release is executed is determined by the version number.
+# GPG Keys #
 
 To make a release you must have the `devs@cucumber.io` GPG private key imported in gpg2.
 
@@ -84,12 +76,3 @@ for example:
     </profiles>
 </settings>
 ```
-
-
-# Deploy the release #
-
-```
-mvn release:perform -Psign-source-javadoc -DskipTests=true
-```
-
-Go into [Nexus](https://oss.sonatype.org/) and inspect, close and release the staging repository.