1. Pre-release steps:

• clear up old instance of Magnolia, configure it again with new settings, migrate data

2. Release steps:

• merge changes from QA to PROD on https://svn.jboss.org/repos/cms/prod/theme/
• merge changes from QA to PROD on https://svn.jboss.org/repos/cms/prod/cs-theme/
• merge changes from QA to PROD on https://svn.jboss.org/repos/cms/prod/magnolia/
• merge changes from QA to PROD on https://svn.jboss.org/repos/cms/prod/forge/portal-content/feeds/
• merge changes from QA to PROD on https://svn.jboss.org/repos/cms/prod/forge/portal-content/default/theme/jsp/org/
• turn off access to author instance of magnolia and move the rest of data to the new instance
• switch Apache to the new magnolia instance
• Put modified ui-components.xml to the WEB-INF/classes
• Install HF URL plugin version 1.1.0 plugin (including rewrite rules)
• Uninstall Developer spotlight CS plugin
• Add Apache rewrite rule (see ORG-202)

3. Rollback steps:

• Common header - revert back to previous SVN revision
• CS theme - revert back to previous SVN revision
• Remove WEB-INF/classes/ui-components.xml
• Install HF URL plugin version 1.0.0 plugin (including rewrite rules)
• Remove added rewrite rule
• switch apache back to the previous Magnolia instance

4. Post release steps:

• create a 3.2.0 tag of https://svn.jboss.org/repos/cms/prod/theme/
• create a 3.2.0 tag of https://svn.jboss.org/repos/cms/prod/cs-theme/
• create a 3.2.0 tag of https://svn.jboss.org/repos/cms/prod/magnolia/
• create a 3.2.0 tag of https://svn.jboss.org/repos/cms/prod/forge/portal-content/feeds/
• create a 3.2.0 tag of https://svn.jboss.org/repos/cms/prod/forge/portal-content/default/theme/jsp/org/