Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <4E269AF5.3010905@epimorphics.com>
Date: Wed, 20 Jul 2011 10:08:05 +0100
From: Ian Dickinson <ian@epimorphics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64;
 rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: jena-dev@incubator.apache.org
Subject: Updating the web site
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The staging version of the project web site is here:

http://jena.staging.apache.org/jena/

To update this, you need to commit changes to the site svn:

https://svn.apache.org/repos/asf/incubator/jena/site/trunk/

The "easy" way to do so is to use the edit facilities of the Apache CMS, 
which are a bit basic but do work. Since each session is authenticated 
to an ASF committer, I can't give the direct link. You have to go via 
the index page:

https://cms.apache.org/

and click through jena/Get jena working copy.

The alternative is to check out the entire svn trunk locally, edit, then 
commit the changes back. The buildbot notices the commit and does the 
actual publishing to the staging server. There's a separate URL to 
publish from staging to production (available from the CMS link, above)

For reference, the CMS manual, such as it is, is here:

http://www.apache.org/dev/cmsref.html

There are instructions on that page for installing the CMS tools 
locally, so that if you're editing a local copy of the entire svn tree, 
you can see what you've done before it gets committed back to svn.

It's entirely possible that the CMS front end and the 
edit-the-entire-svn-trunk methods will play nice together. Otoh, the CMS 
was written fron scratch in about two weeks. Keep checking that you are 
at the svn head!

Ian