...
- Check out site src code
Code Block svn co https://svn.apache.org/repos/asf/struts/site/ struts-site
- Update xml files
- struts-site/src/site/xdoc/announce.xml (if applicable, refer also to corresponding security bulletin)
- struts-site/src/site/xdoc/downloads.xml (remove previous version)
- struts-site/src/site/xdoc/download.xml (remove previous version)
- struts-site/src/site/xdoc/index.xml
- struts-site/src/site/site.xml
- Commit the changes
- Generate the site
Code Block mvn site:site
- Open
struts-site/target/site/index.html
and verify the urls and versions are right - Deploy site
It takes a few hours for the site changes to go liveCode Block mvn site-deploy
Redeploy the draft docs
Make public available all the pages that could leak confidential information about the vulnerability. Wait or manually export the space in Confluence. Build snapshot locally and copy assembly/target/assembly/out/struts2-#.#.#-SNAPSHOT-docs.zip to people.apache.org and update /www/struts.apache.org/2.x/docs
Permissions
After updating the site, be sure that the permissions are set to group writeable ($ chmod -R g+w .
and $chown $ chown -R :struts .
)
Post announcements
...