On Jan 2, 2008 4:05 PM, Marshall Schor <[EMAIL PROTECTED]> wrote: <snip>
> Since we want our docs pages to refer not only to the "current release" > but also previous releases, it would be good to figure out a fairly > automatic system for this. (That was a virtue of the /dist/ - archive > system - we could point the previous releases doc links to a directory > containing all the releases, and wouldn't need to update this link for > subsequent releases). > > The other thing to do is to figure out how to keep the archived things > on our web-site. It was suggested that we should do this like we handle > the web-site checkout. > Probably the straight-forward thing to do is to have a special directory > where all the docs we want to refer to live, have the archive link point > there, and have special links that refer to the "current version". probably better to use a symbolic link rather than a .htaccess > As I recall, the web-site, itself, is replicated to other servers (since > after you update it , you have to wait a while for it to appear). yep > I have to confess that this seems quite wasteful of disk resources > (double+ copies of things like javadocs - one in SVN, one on > people.apache.org in our web-site place, and maybe (several?) additional > copies on web-servers used for incubator.apache.org/uima). disc's cheap :-) bandwidth and server load are usually the most important factors AIUI having lots of duplicates allows low downtime. even if minotaur takes a tumble, ajax is able to step up almost immediately. > But Robert Donkin suggested this was the best way. i talked it over the the infra team and their strong recommendation was to store in svn and then checkout onto the website - robert
