Growthcraft Release Process

#DRAFT DRAFT DRAFT

###Release Schedule

Generally we are looking to have a bi-monthly stable release until we start to thin out all the feature requests. Our current focus is Growthcraft 2 (MC1.7.10) and will soon be adding Growthcraft 3 (MC1.8/1.9), but we will still keep Growthcraft 2 updated until the mass community moves to MC1.8/1.9.

###Versioning Scheme

http://semver.org/

1. MAJOR version when you make incompatible API changes. This would be a change in forge version.
2. MINOR version when you add functionality in a backwards-compatible manner.
3. PATCH version when you make backwards-compatible bug fixes.

Growthcraft 3 will be for Minecraft 1.8

###Producing a Release Candidate (Snapshot)

After all of the pull requests have been merged into the development branch, the version needs to be updated in the .travis.yml and the build.gradle. Wait for Travis-CI to successfully build.

###Producing a Stable Release

Tag the release. This is needed so the Travis-CI can push the artifacts back to github and place it into the correct release notes page.

###Test the Release

Using what was produced by Travis-CI and posted to the releases page, test to make sure the that module works.

###Uploading to Curse Forge

1. Upload the growthcraft-[version]-bundled.jar first.
2. Then Upload the growthcraft-[version]-complete.jar.