Hi, yes, this is what I'm thinking, too. How about a svn location for this like this:
https://svn.apache.org/repos/asf/uima/site/ << exists archive/docs/d << new -Marshall On 10/1/2018 11:16 AM, Richard Eckart de Castilho wrote: > On 1. Oct 2018, at 15:36, Marshall Schor <[email protected]> wrote: >> It's true, that with some work, one could download archive dists and unpack >> them, and get these artifacts, but I thought that since we've already done >> that >> and they are already in SVN, why not keep a semi-convenient way to get to >> these, >> for our users who might still be using an older release? > The latest documentation should always be accessible by the > "[product]-current" URLs > which can be hard-coded on the documentations page (i.e. no change to the > uima-site necessary > here when a release is performed) > > https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimaj-current/index.html > https://svn.apache.org/repos/asf/uima/site/trunk/uima-website/docs/d/uimafit-current/tools.uimafit.book.html > ... etc. > > The "[product]-current" folders are created via a "svn copy" command after > checking in the docs for > a new release. > > We could avoid having all the old docs checked out whenever we want to edit > the site by moving > the whole "docs/d" folder e.g. to "site/archive" and including a link to > > https://svn.apache.org/repos/asf/uima/site/archive/site/archive/docs/d > > on the downloads and/or documentation page to point to old versions. > > Since the website is in SVN, the user can conveniently browse the tree > and access the HTML files (e.g. APIDocs) inside it. > > We'd then only retain the "[product]-current" ones under > "uima/site/trunk/uima-website/docs/d". > > I think we don't need to tag the entire website just to archive the old docs. > > Cheers, > > -- Richard > >
