I do not understand about the wget stuff, but we could simply take the
live versions of the docs from the directory where they are currently
served from and create a .zip and a .tar.gz from them. Then we could
create a directory on archive.apache.org, e.g.
http://archive.apache.org/dist/db/torque/docs
and put the zipped and tar.gz'ed versions there. The policy says we must
sign them, so a .md5 and a .asc will go along.
Then we could put a link to this into
http://db.apache.org/torque/documentation/previous-releases.html
We'd keep only an arcive of the docs of the current production release.
If nobody objects, I could prepare this by removing the links to older
versions of the docs in the current site. After the site is published
again in RC3, we can then to the zipping, signing and removing.
Thomas
On Tue, 20 Mar 2007, Greg Monroe wrote:
Having the old site/docs available would be nice. But
I don't think they should be online since it leads to
Google searches finding old/invalid info that people don't
realize it's from and archived site.
How about doing the following on each old version to create
a torque-site-X.x.x.zip that could be downloaded from the
archive site.
wget -r -k -np
http://db.apache.org/torque/releases/torque-3.1/index.html
Then copy the maven*.css files to the styles directory created
under the db.apache.org/torque/releases/torque-3.1 directory.
I just did this for 3.1 and it looks usable from from my
hard drive.
For future versions we could generate a site source zip from
the site project's target docs directory.
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
