Releasing

Owned by ScottS
Last updated: Jun 07, 2016 by Misagh Moayyed

New CAS documentation site

CAS documentation has moved over to apereo.github.io/cas, starting with CAS version 4.x. The wiki will no longer be maintained. For the most recent version of the documentation, please refer to the aforementioned link.

Releasing the CAS Server is a relatively straightforward process. Here are the current steps:

  1. Ensure there are no open issues in JIRA
  2. If its a relatively major release (i.e. 3.X), make sure that at least one RC has been released. Minor releases (i.e. 3.3.X) don't generally require an RC.
  3. Ensure that it builds
  4. Update the pom.xml files to move from -SNAPSHOT to the actual release version.
  5. Ensure that documentation is updated to reflect all changes.
  6. Tag the release in SVN following the standard conventions
  7. Build for Maven2 Deployment with the following (this assumes that you have permission to post to the Jasig Repository):
    • mvn clean package install source:jar javadoc:jar deploy:deploy
  8. Build for Jasig Download Deployment
    • mvn clean package install source:jar javadoc:jar assembly:assembly
  9. SFTP files to Jasig Server
  10. Request that CAS release manager add the release to the download portion of the web site
  11. Post announcement on web site as CAS *and* Jasig News
  12. Send announcement to cas-announce, cas-dev, cas-user
  13. Make sure Jasig Newsletter Editor knows about release by sending the announcement to news at jasig dot org.