A better concept I think would be to have one alternative site, which kept all of the versions "visible". I'm not sure how to do this without some amount of manual copying; maybe someone else knows how?
-Marshall On 9/29/2018 6:03 PM, Marshall Schor wrote: > +1. I thought I had done some of this some time ago. > > We could also do some cleanup of our website, because each release includes > typically putting up a javadoc set of files, which can be large. > > We currently have for the uima-site, this svn address > > .../uima/site/trunk/uima-website/... (e.g. docs/d/uimaj-x.y.z/apidocs, etc) > > How about we create > > .../uima/site/tags/uima-website-archive-2018-10-1/ or whatever, as a copy of > the > uima-website, right before we do an svn delete of some older versions? That > way, we would have an easy access (if ever needed) to what got deleted > (without > taking up more svn space)? > > -Marshall > > On 9/27/2018 12:51 PM, Richard Eckart de Castilho (JIRA) wrote: >> Richard Eckart de Castilho created UIMA-5874: >> ------------------------------------------------ >> >> Summary: Archiving old releases >> Key: UIMA-5874 >> URL: https://issues.apache.org/jira/browse/UIMA-5874 >> Project: UIMA >> Issue Type: Improvement >> Reporter: Richard Eckart de Castilho >> >> >> It seems we have basically *all* our old releases still in the dist spot - >> but Apache says we should only keep around the latest releases: >> >> http://www.apache.org/legal/release-policy.html#how-to-archive >> >> How about deleting some old releases and just keeping the latest ones for >> each product in the UIMAv2 and UIMAv3 versions (if available).? >> >> >> >> -- >> This message was sent by Atlassian JIRA >> (v7.6.3#76005) >>
