Page History

...

Your Maven settings (~/.m2/settings.xml) file should have the following (note: curator-website-checkout-path is used as a temporary path when deploying the Curator website):

<settings>
    ...
    <servers>
        ...
        <server>
            <id>apache.website.svnpub</id>
            <username>Your Apache Username</username>
            <privateKey>${user.home}/.ssh/id_rsa</privateKey>
        </server>
        ...
    </servers>

    <profiles>
        <profile>
            <properties>
                ...
                <curator-website-checkout-path>path-goes-here</curator-website-checkout-path>
    	        <gpg.keyname>id-of-your-pgp-key</gpg.keyname>
                ...
            </properties>
            ...
        </profile>
        ...
    </profiles>
    ...
</settings>

...

1. These files must be put into the release directory (svn co https://dist.apache.org/repos/dist/release/curator/)
   • Create a directory for the release
   • cp the files to this directory and then svn commit
2. Release the binary artifacts
   • Go to: https://repository.apache.org/index.html
   • Select the curator release and click the "Release" button.
3. Announce the release (see Example Emails) to these mailing lists:
   • user@curator.apache.org
   • dev@curator.apache.org
   • general@apacheannounce@apache.org
   • user@zookeeper.apache.org
4. Update the Releases Wiki: https://cwiki.apache.org/confluence/display/CURATOR/Releases
5. Update Jira: https://issues.apache.org/jira/browse/CURATOR/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel

...

...

Assuming you have a clean compile/install of Curator, from the root of the Curator directory:

mvn site site:stage

Have a look at the staged site and make sure it's good. Then:

mvn site-deploy

You'll need to make sure you've authenticated to the Apache Subversion server before you can push the site, else you may get an error along the lines of authorization failed: Could not authenticate to server: rejected Basic challenge. More reading material on how to secure your SVN credentials can be found here.

Also note if you get an error complaining that Server certificate verification failed: issuer is not trusted, you can add the repo certificate to the list of certificates accepted to your local svn client by simply listing the repository and accepting the cert permanently.

svn list https://svn.apache.org/repos/asf/curator/site/trunk

Error validating server certificate for 'https://svn.apache.org:443':
 - The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 - Hostname: *.apache.org
 - Valid: from Tue, 20 Dec 2011 00:00:00 GMT until Mon, 17 Feb 2014 23:59:59 GMT
 - Issuer: Thawte, Inc., US
 - Fingerprint: bc:5f:40:92:fd:6a:49:aa:f8:b8:35:0d:ed:27:5e:a6:64:c1:7a:1b
(R)eject, accept (t)emporarily or accept (p)ermanently? p