Releasing the LDSTech IDE

This document is meant to describe the steps involved in doing a release of the LDSTech IDE. This is mostly for internal use - if you are just using the LDSTech IDE, this probably isn't something you care about.

Steps to release the IDE:

  1. Make sure you have a good build that has been tested by other members of the team.
  2. Tag the release in Subversion
  3. Move the 'current' symbolic link to your new version (ie, from 1.1.3 to 1.2)
  4. Replace the current update/e37-thirdparty with update/e37-thirdparty-dev
  5. Copy the latest update/<version>/<buildnumber> directory to update/e37
  6. Go into Nexus and Expire the cache for "downloads/lds-tech-ide/update"
  7. Release the version in JIRA
  8. Publish release notes to SharePoint, the LDSTech Forums, and our Twitter account
  9. Update your versions in trunk - note, you can't just modify the version in the POMs, you must also edit the MANIFEST.MF for any plugin, and anything that references that version. It will be in a slightly different format than a typical Maven version. For example, for 1.2.0, it would be something like 1.2.0-SNAPSHOT in Maven and 1.2.0.qualifier in anything Eclipse uses.
  • Don't forget to set the versionTag property in the root pom.
  • Update all *-SNAPSHOT versions
  • Update all *.qualifier versions
This page was last modified on 27 April 2012, at 16:06.

Note: Content found in this wiki may not always reflect official Church information. See Terms of Use.