THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Code Block |
|---|
ssh people.apache.org
cd /www/people.apache.org/builds/struts/$VERSION
cp struts-$VERSION-src.* /www/www.apache.org/dist/struts/source
cp struts-$VERSION-docs.* /www/www.apache.org/dist/struts/documentation
cp struts-$VERSION-lib.* /www/www.apache.org/dist/struts/library
cp struts-$VERSION-apps.* /www/www.apache.org/dist/struts/examples
cp struts-$VERSION-all.* /www/www.apache.org/dist/struts/binaries
|
If a new DTD was defined, add it to https://svn.apache.org/repos/asf/struts/site/trunk/pom.xml, in get-dtds execution section.
| Note |
|---|
| The default setup on people.apache.org will leave the files and directories only changeable by the user who creates them. The last two steps will allow future releases to go smoothly. |
Promote release
Log in again to Nexus and release the repository, it will be automatically replicated across Maven Repositories
See Releasing a Maven-based project for further details.
...
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 Update xml files
- struts-site/src/site/xdocsource/announce.xml md (if applicable, refer also to corresponding security bulletin)
- struts-site/src/sitesource/xdoc/downloads.xml (remove previous versionhtml (Prior Releases section)
- struts-site/src/site/xdoc/download.xml (remove previous versionsource/index.html (some parts will updated automatically with values defined in
_config.yml) - struts-site/src/site/xdoc/indexsource/archetype-catalog.xml
- struts-site/src/site/site.xml
- Generate site with Jekyll
jekyll build- with
jekyll serve -wyou can check the generated site at http://localhost:4000struts-site/src/site/resources/archetype-catalog.xml
Commit the changes and the generated contentGenerate the site
Now the changes must be deployed to production which is basically a separated Subversion repository, you check it out with command below:
| Code Block |
|---|
...
svn co |
...
https://svn.apache.org/repos/infra/websites/production/struts/content struts-production |
It's a good idea to keep that working copy to be used with future releases. Right now copy content of struts-site/content to struts-production, then commit changes. Next step is to update exported wiki pages. With current approach the pages are kept in struts-production/release/2.X.x/docs where X is the current branch (ie. 2.3.x, 2.2.x and so on). Simply remove the whole content from under /docs and update it with docs from assembly (you can download one from Maven repository or copy generated during release process which supposes to be in struts/assembly/target/cwiki). And commit changes.
Deploy site
| Code Block |
|---|
mvn site-deploy
|
...
Redeploy the draft docs (Optional)
...