Creating a Release

To release Amidst, follow these steps:

1. Update the metadata on master

• checkout the branch master
• update information in src/main/resources/amidst/metadata.properties
• update wrapper information in /travis-ci/{wrapper-for-mac, wrapper-for-windows}/pom.xml
• commit and push

2. Update the branch releases

• checkout the branch releases
• fast-forward merge the branch master into the branch releases
• push

3. Create the new release tag

• create and push the tag
• tags are named like this:
  • v4.0 for stable releases
  • v4.0-beta5 for pre-releases

4. Update the release information on Github

• wait for travis ci to build Amidst, it will attach the executable jar, zip and exe files to the release on Github
• add meaningful release notes
• make it a pre-release, if necessary

5. Update the update document (only if not a pre-release)

• the update document is used by Amidst to check for updates
• if you have write access, you can edit the update document here
  • https://github.com/toolbox4minecraft/amidst/blob/gh-pages/api/update-information.json
• to generate the update document, you can use the devtool GenerateUpdateInformationJson
  • it uses the information from the file src/main/resources/amidst/metadata.properties
  • you can add an optional message which is displayed to the user, use this with care

6. Update the Amidst entry in the Minecraft wiki (only if not a pre-release)

7. Update third party package managers (only if not a pre-release)

• for homebrew cask there seems to be a third party that updates the package information
  • #128
  • https://github.com/caskroom/homebrew-cask/blob/master/Casks/amidst.rb