This text assumes that the version number for a release is X.Y.Z.
-
Make sure
CHANGELOG.md
is up to date. Cross-check with GitHub Issues for given milestone. -
If needed:
git commit -m "add missing changelog entries"
. -
Reorder the entries in
CHANGELOG.md
from most important to least. Up to this point, entries are typically added chronologically. This is not the best order for release. -
Pick a code name and update the heading of the latest changelog section. It should look like
X.Y.Z [Code Name](link) (YYYY-MM-DD)
instead ofX.Y.Z (not yet released)
. -
Update the latest version number in
README.md
. -
git commit -m "prepare for the X.Y.Z release"
. -
Your workspace should now be pristine. Check with
git status
. -
Make sure that your
JAVA_HOME
points to Java 8. Check with$JAVA_HOME/bin/java -version
. -
mvn release:prepare -Pwildfly10
-
Maven will ask 3 questions. You might want to manually enter X.Y.Z as an answer to the 1st question if the default answer is wrong. Default answers to the 2nd and 3rd questions are always OK.
-
mvn release:perform -Pwildfly10
-
Go to
https://repository.jboss.org/nexus/index.html#stagingRepositories
-
Find the correct staging repository; it will be called
wildfly_extras-NNNN
. Verify the owner name; it should be your JBoss.org username. Also check the content of the repository. -
Close the staging repository. Nexus will perform some validations. If successful, Nexus will send a confirmation e-mail.
-
Release the repository. Nexus will send another confirmation e-mail.
-
Create a GitHub Release.
-
Close the relevant GitHub Milestone. Optionally create a new Milestone.
-
Add a new heading to the top of
CHANGELOG.md
. Its text should be:X.Y.Z+1 (not yet released)
. -
git commit -m "add next version number to changelog"
-
Send a release announcement.