Hi all, I asked Infra (https://issues.apache.org/jira/browse/INFRA-5631)
to pull the switch to move our website to the Apache CMS, and here it
is: http://roller.apache.org/. The local build (the headache that Dave
and I went through earlier with the Perl and Python libraries) described
in #1 here: http://roller.apache.org/downloads/edit_website.html doesn't
really need to be done anymore, just SVN commit your changes (which were
relocated to roller/cmssite/trunk per Infra's request) and within a few
seconds http://roller.staging.apache.org
<http://roller.staging.apache.org/>will show the latest updates. If
you're happy with what you see then go to
https://cms.apache.org/roller/publish (link is on
<http://roller.staging.apache.org/downloads/edit_website.html>http://roller.apache.org/downloads/edit_website.html)
and then hit "Publish" to move it to roller.apache.org. Presently only
Roller committers may publish the Roller website (makes sense) but we
have the option of allowing any Apache committer to publish it.
Apache CMS *might* have a Wiki-like capability to update the pages
without changing what we have in SVN (I don't know), but I'd like to ask
that for now we just update the SVN so it's always in sync with the
website. It's so easy now to see the results and publish them that that
shouldn't be a problem.
Unless I hear any objections I'll delete our old trunk/site folder soon,
as we're no longer using it.
Also, on our Confluence Wiki, I'd like to remove the "What's New In
Roller 4.0" page from 2007 (
https://cwiki.apache.org/confluence/display/ROLLER/What%27s+New+in+Roller+4.0)
as it's a bit old hat now. Any objections? Moving forward, I'm seeing
new pages in Confluence collecting tips for each server and database
that Roller runs on.
Regards,
Glen
<http://roller.staging.apache.org/>
