+1 to archive them (legacy/attic dir) to start. - Ray
On Fri, Aug 21, 2020 at 3:33 AM Jean-Baptiste Onofre <[email protected]> wrote: > Hi, > > It sounds like a good idea to have legacy/attic folder. If after some > months, we don’t have any feedback, we will delete. > > Regards > JB > > > Le 21 août 2020 à 09:05, Romain Manni-Bucau <[email protected]> a > écrit : > > > > Is pushing all these legacy pages in a legacy/ folder (manually, does not > > need to be automatized) and if anyone complains about this lack then we > add > > it back otherwise we just keep them hanging in a folder? > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <https://rmannibucau.metawerx.net/> | Old Blog > > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > < > https://www.packtpub.com/application-development/java-ee-8-high-performance > > > > > > > > Le ven. 21 août 2020 à 08:31, David Jencks <[email protected]> a > > écrit : > > > >> There are some quite old pages in the website that are in html, about > the > >> CT test results from the 0.2, 0.3, and 1.0.0 releases. An example is > >> > https://aries.apache.org/downloads/ct/0.3/org.osgi.test.cases.blueprint.html > >> < > >> > https://aries.apache.org/downloads/ct/0.3/org.osgi.test.cases.blueprint.html > >. > >> FWIW, the link to this page in the current site is broken. > >> > >> Could we drop these? I can convert them to appear in the Antora site, > but > >> it would take a few hours and increase the compexity of the UI bundle, > so > >> if there’s agreement to drop them as obsolete I’d rather not put in the > >> time. > >> > >> I think this is all the relevant files in the current website: > >> > >> /downloads/ct/current-release/org.osgi.test.cases.transaction.html > >> /downloads/ct/current-release/org.osgi.test.cases.blueprint.secure.html > >> /downloads/ct/current-release/org.osgi.test.cases.jmx.html > >> /downloads/ct/current-release/org.osgi.test.cases.jndi.html > >> /downloads/ct/current-release/org.osgi.test.cases.blueprint.html > >> /downloads/ct/current-release/org.osgi.test.cases.blueprint.java5.html > >> /downloads/ct/0.2-incubating/org.osgi.test.cases.transaction.html > >> /downloads/ct/0.2-incubating/org.osgi.test.cases.blueprint.secure.html > >> /downloads/ct/0.2-incubating/org.osgi.test.cases.jmx.html > >> /downloads/ct/0.2-incubating/org.osgi.test.cases.jndi.html > >> /downloads/ct/0.2-incubating/org.osgi.test.cases.blueprint.html > >> /downloads/ct/0.2-incubating/org.osgi.test.cases.blueprint.java5.html > >> /downloads/ct/0.2-incubating/testresults.html > >> /downloads/ct/0.3/org.osgi.test.cases.transaction.html > >> /downloads/ct/0.3/org.osgi.test.cases.blueprint.secure.html > >> /downloads/ct/0.3/org.osgi.test.cases.jmx.html > >> /downloads/ct/0.3/org.osgi.test.cases.jndi.html > >> /downloads/ct/0.3/org.osgi.test.cases.blueprint.html > >> /downloads/ct/0.3/org.osgi.test.cases.blueprint.java5.html > >> /downloads/ct/0.3/org.osgi.test.cases.jndi.secure.html > >> /downloads/ct/0.3/testresults.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.transaction.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.blueprint.secure.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.jmx.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.jpa.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.jndi.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.blueprint.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.blueprint.java5.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.jndi.secure.html > >> /downloads/ct/1.0.0/org.osgi.test.cases.jndi.43.html > >> > >> > >> The “current-release” ones don’t seem to be in the current > >> aries-antora-site repo, so I suspect they are not generated through CMS > but > >> through some other unknown process. My impression of the svn website > >> publishing is that if someone just commits a page to it using some > process > >> it stays forevermore unless it is explicitly removed. Otherwise I made > a > >> mistake somewhere. > >> > >> Thanks > >> David Jencks > > -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay)
