THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Log on to people.apache.org
- Go to /x1/www/www.apache.org/dist/incubator/empire-db
- Create a subdirectory with the version number (i.e. 2.0.5)
- Copy all distribution files from your home directory to that directory (.zip, .tar.gz, .asc, .md5, .sha)
- Possibly change write permissions of that directory and all files to allow group members to add / modify files (although they should never ever change again)
- remove all old releases from the dist folder (only one release per branch allowed)
- Wait (one day) before files become available on the mirrors
...
- Check out the Empire-db website source files from https://svn.apache.org/repos/asf/incubator/empire-db/site
- Edit Pages with html editor (I am using Microsoft Expression Web)
- Open page downloads/latest.htm and copy section with previous release files to downloads/previous.htm.
- In downloads/latest.htm replace all reference to old version number with new version number.
- Update news.html
- so a svn delete on javadocs/empire-db
- commit
- recreate the empire-db folder
- fetch the new javadoc jar from http://repo1.maven.org/maven2/org/apache/empire-db/empire-db/2.0.7-incubating/empire-db-2.0.7-incubating-javadoc.jar
- extract into the javadocs/empire-db folder
- svn add the empire-db folder
- Commit all changes to svn repo.
- Log on to people.apache.org using ssh
- Goto /x1/www/incubator.apache.org/empire-db
- Run "svn update" command.
- Don't forget to add write permissions of all changed files for group and all users (change from 0x644 to 0x664)
- Wait some time for changes to become available on the mirrors.
- Remove all old releases from the /www/www.apache.org/dist/incubator/empire-db folder, only one (latest) release per branch allowed.
Announce release
Send an E-Mail to announce@apache.org
...