Skip to content

Release process

Paweł Pastuszak edited this page Sep 11, 2015 · 52 revisions

This page contains some information on how to do Vis releases and is probably completely irrelevant for you.

VisUI:

  1. Change pom.xml version: remove SNAPSHOT
  2. Check VisUI.version
  3. Do mvn clean deploy -P release
  4. Update pom.xml with next version with SNAPSHOT
  5. Update VisUI.version
  6. Update CHANGES
  7. Commit changes
  8. Update USL
  9. Update Github Wiki Page
  10. Create new release on GitHub
  11. Write blog post, update GitHub release
  12. PR LibGDX

VisParent:

  1. Remove snapshot from version
  2. Do mvn clean deploy -P release
  3. Set new version with snapshot
  4. Commit changes

VisEditor:

  1. Update POMs and App.version
  2. Disable Jenkins projects: runtime, editor-edge
  3. Release runtime mvn clean deploy -P release
  4. Commit changes, and build editor new stable and beta
  5. Create release on github
  6. Update POMs and App.version with new version, update CHANGES, project converters
  7. Re enable projects
  8. Commit changes
  9. Update website, twitter, irc, etc.