Skip to content

Latest commit

 

History

History
20 lines (20 loc) · 1.25 KB

release-procedure.md

File metadata and controls

20 lines (20 loc) · 1.25 KB
Raw
  1. Make sure any new modules are included
  2. Make sure the parent pom includes any new modules.
  3. Make sure the top pom includes any new modules.
  4. Replace all instances of old_version with new_version (do a replaceAll operation, note that maven-release-plugin isn't viable until ENUNCIATE-501 is fixed, which depends on MRELEASE-669)
  5. mvn clean install (to run all the tests)
  6. Commit and tag (e.g. git tag -a v2.0.0 -m "Version 2.0.0").
  7. mvn clean deploy -P release (your new version should now be deployed)
  8. Build the distribution from the LAST RELEASE TAG (e.g. ant -f build-site.xml dist)
  9. Push.
  10. Reset HEAD to a snapshot version.
  11. Create the release.
  12. Make any announcements.
  13. Do a "replace all" of old_version to new_version in the wiki. (e.g. find . -name "*.md" | xargs sed -i 's/2.0.0/2.0.1/g')
  14. Upload any new schemas to the pages.
  15. Update the Getting Started Sample.
  16. Update and publish the Gradle Plugin.
  17. Update build.gradle to the new version
  18. ./gradlew publishPlugins
  19. Update the docs. (e.g. find . -name "*.md" | xargs sed -i 's/2.0.0/2.0.1/g')