I'd be inclined to update the downloads page AND add a depreciation badge. IMO these are two different use cases, people visiting the downloads site are looking for a bundle to install into their Sling instance whereas people looking at the Github site are looking for the code / to contribute. We should inform them in both cases.
How does this look for a deprecation list on the downloads page: https://imgur.com/a/dYxXKp7 Does deprecated seem like the right term? Or obsolete? On Wed, May 23, 2018 at 9:57 AM, Bertrand Delacretaz <[email protected] > wrote: > On Wed, May 23, 2018 at 9:34 AM, Robert Munteanu <[email protected]> > wrote: > > ...That's a very good idea. Would it make sense to add "(Deprecated)" or > > "(replaced by ...)" next to this entry?... > > Or add a deprecation badge at [1] ? > > I meant to use GitHub Topics for such things but we're not allowed to > change them, so we might define a few badges for "contrib", > "deprecated" etc. instead. and add them at the top of READMEs. > > I'm thinking of badges like the "contrib" one that I tried at > https://github.com/apache/sling-org-apache-sling-launchpad-contrib-testing > . > We might store such badges as svg files under > http://sling.apache.org/badges and refer to them from README files. > > -Bertrand > > [1] https://github.com/apache/sling-org-apache-sling-starter-content >
