-
Notifications
You must be signed in to change notification settings - Fork 130
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:
- Change pom.xml version: remove SNAPSHOT
- Check
VisUI.version
- Do
mvn clean deploy -P release
- Update pom.xml with next version with SNAPSHOT
- Update
VisUI.version
- Update CHANGES
- Commit changes
- Update USL
- Update Github Wiki Page
- Create new release on GitHub
- Write blog post, update GitHub release
- PR LibGDX
VisParent:
- Remove snapshot from version
- Do
mvn clean deploy -P release
- Set new version with snapshot
- Commit changes
VisEditor:
- Update POMs and App.version
- Disable Jenkins projects: runtime, editor-edge
- Release runtime
mvn clean deploy -P release
- Commit changes, and build editor new stable and beta
- Create release on github
- Update POMs and App.version with new version, update CHANGES, project converters
- Re enable projects
- Commit changes
- Update website, twitter, irc, etc.
See README for VisUI introduction.