Skip to content

Steps to check a version before release

Justin Brubaker edited this page Sep 14, 2017 · 1 revision
  • Make sure final jar runs on newest server version.
  • Make sure you are not op for testing
  • Test all permissions.
  • Test all commands.
  • Test different variations of commands that might effect changes in the proposed release.
  • Test all blacklists and bypasses for those blacklists.
  • Test economy.
  • Check jar naming. (Make sure it follows the "EpicRename vx.x.x.jar" naming convention)
  • Tag the release on github and upload the jar.
  • Upload the same jar to keybase with the hashes of that version. (This allows checking if you have a legit version)
  • Upload the release to spigotmc.org making sure to point out any config changes and new permissions etc.
  • Watch and hope you didn't break anything.
  • Profit
Clone this wiki locally