...
- 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
- struts-site/src/site/resources/archetype-catalog.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 - Got to Struts Staging and review the changes
- If everything is ok, push changes to Production via Apache CMS web interfaceDeploy site
It takes a few hours for the site changes to go liveCode Block mvn site-deploy
Update site (Struts 2 site)
Use below script to perform update
Code Block |
---|
#!/bin/sh # script used to update struts2-subsite after release VERSION=2.3.15 BRANCH=2.3.x TAG=STRUTS_2_3_15 svn co https://svn.apache.org/repos/infra/websites/production/struts/content/ struts-production-site export VERSION=2.3.Xsvn co https://svn.apache.org/repos/asf/struts/struts2/tags/$TAG/ $TAG wget -erobots=off http://people.apache.org/builds/struts/$VERSION/struts-$VERSION-docs.zip unzip struts-$VERSION-docs.zip -d docs cd $VERSION rm -r struts-site/release/$BRANCH/docs rm -r struts-site/release/$BRANCH/struts2-core rm -r struts-site/release/$BRANCH/struts2-plugins rm -r struts-site/release/$BRANCH/xwork-core mv -f docs/struts-$VERSION/docs/* struts-site/release/$BRANCH cd $TAG mvn site:site site:stage -DstagingDirectory=../struts-production-site/release/2$BRANCH cd .3.x/struts-site svn add ./ --force ./ # Delete removed files svn statusst | grep '^\!' | sed 's/! *//' | awk 'BEGIN {FS="\t"};{print "\""$1"\""$2}' | xargs svn deldelete --force svn commit -m "Updates Struts2 subsite after release docs" --no-auth-cacheprocess" cd .. rm -r struts-site rm -r $TAG rm -r docs rm struts-$VERSION-docs.zip |
Post announcements
We leave this as the last step, once the artifacts have had time to sync up on the mirrors.
Announce the release and the vulnerability. Typically this will be sent to the reporter, the project's users list (user@struts.a.o), the project's dev list (dev@struts.a.o), the project's announce list (announcements@struts.a.o), security@apache.org, full-disclosure@lists.grok.org.uk and bugtraq@securityfocus.com.
Samples are available at Sample announcements page.