-
Notifications
You must be signed in to change notification settings - Fork 162
Releasing Forge
Assume that:
REL = Version to be released (eg. 2.5.0.Final)
DEV = Next Version (eg. 2.5.1-SNAPSHOT)
(you must have ssh keys registered with your github account)
For each project, run:
mvn clean release:prepare -DdevelopmentVersion=DEV -Dtag=REL -DreleaseVersion=REL mvn release:perform -Darguments=-DskipTests
Where LAST_TAG is the tag before the released tag:
git shortlog LAST_TAG..HEAD -n
Also available here: https://github.com/forge/core/graphs/contributors
-
Update the metadata version in https://github.com/forge/website-data/blob/master/metadata.yaml
-
Add a new entry in https://github.com/forge/website-data/blob/master/news.yaml
-
Create a new entry in https://github.com/forge/docs/tree/master/news
-
Update JBoss Tools plugin: https://github.com/jbosstools/jbosstools-forge
-
Update and release Intellij IDEA plugin: https://github.com/forge/intellij-idea-plugin/ - http://plugins.jetbrains.com/plugin/7515
-
Update and release Netbeans plugin: https://github.com/forge/netbeans-plugin - http://plugins.netbeans.org/edit-binary/id/3921
-
Command:
mvn clean release:prepare release:clean -Prelease -Darguments="-DskipTests -Dkeystore.path=<KEYSTORE_PATH> -Dkeystore.password=<PASSWORD>" -DreleaseVersion=<REL> -Dtag=<REL> -DdevelopmentVersion=<DEV>
-
-
Update Homebrew: https://github.com/Homebrew/homebrew-core/blob/master/Formula/jboss-forge.rb
-
Update FORGE_VERSION in Docker: https://github.com/jboss-dockerfiles/forge/blob/master/Dockerfile
-
Tag the repo when you want to release new version and ping mgoldmann on IRC (#jboss-docker on Freenode) so he can kick a new build.
-