Release Process

The following are the instructions for releasing a new version of wildfly-installation-manager-api:

1. Merge your changes and rebase on top of the latest upstream.
2. Bump the project version to the desired one by removing the -SNAPSHOT suffix.
3. Commit the change with the following message structure, for example, if you are releasing 2.0.0.Final:

   git commit -am "Prepare for 2.0.0.Final release"
   

4. Build and deploy the project to Nexus by enabling the jboss-release maven profile:

   mvn clean deploy -Pjboss-release
   

5. Navigate to https://repository.jboss.org/nexus/index.html and close the staged repository
6. Delete from your local maven cache the version you have deployed to Nexus so it can be forced to be downloaded again:

find $HOME/.m2/repository/org/wildfly -name "*installation-manager*" -type d -exec rm -rf {} \;

Alternatively, you can use mvn -U in the next step.

1. Test the dependent projects with -Pstaged-releases maven profile activated, so the recently staged version can be retrieved from Nexus staging repos.
2. Release the staged repository in Nexus.
3. Tag the current branch, e.g:

   git tag 2.0.0.Final
   

4. Bump the project version to the next one adding a -SNAPSHOT suffix to the desired version. E.g 2.0.1.Beta1-SNAPSHOT
5. Commit the change with the following message structure:

   git commit -am "Next is 2.0.1.Beta1"
   

6. Push the upstream main branch and the tag:

   git push upstream main 2.0.0.Final
   

7. Enjoy an adult beverage of your choice.