Page History

...

Wait 24 hours before proceeding.

...

Update

...

If the release will fix a - hopefully yet undisclosed - security issue, it's now time to update the Security Bulletins page and add a new announcement. For a template, just check former announcements

Update site

• Check out site src code

  Code Block
  svn co https://svn.apache.org/repos/asf/struts/site/ struts-site

• If a new DTD was defined, add it to source/dtds
• Update current version and release date in struts-site/_config.yml
• Update page source files
  • struts-site/source/announce.md (if applicable, refer also to corresponding security bulletin)
  • struts-site/source/downloads.html (Prior Releases section)
  • struts-site/source/index.html (some parts will updated automatically with values defined in _config.yml)
• Generate site with Jekyll
  • jekyll build
  • with jekyll serve -w you can check the generated site at http://localhost:4000

• Commit the changes and the generated content

...

Redeploy the draft docs (Optional)

...

• Checkout source of the website and export Confluence pages

  Code Block
  svn co https://svn.apache.org/repos/asf/struts/site/trunk struts-site cd struts-site mvn package

  Now the whole Confluence space is exported to target/cwiki/WW/docs/

• Checkout copy of production website

  Code Block
  svn co https://svn.apache.org/repos/infra/websites/production/struts/content/ struts-production

  (you can checkout just a subtree, but it's better to checkout the whole repo especially when you want to update also the main web page)

• Update production

  Code Block
  cp -r struts-site/target/cwiki/WW/docs/* struts-production/development/2.x/docs/ cd struts-production svn commit "Updates production"

Post announcements

We leave this as the last step, once the artifacts have had time to sync up on the mirrors. Target it to: user@struts.a.o and announcements@struts.a.o, samples are available at Sample announcements page