The following procedure is recommended to deprecate Sling Git repositories, indicating that they should no longer be used.
maintenancewith the last version before deprecation.
masterbranch, keeping just
deprecatedGitHub topic to the module, using a .asf.yaml file in the
Deprecated modules can then be found with a GitHub query, see below.
The reasoning is that keeping just a
README file makes it obvious that the repository is deprecated, and having the
maintenance branch makes it easy to get the deprecated code and even make maintenance releases if desired.
A deprecated module can be un-deprecated if the Sling PMC agrees to do that, technically it just means reverting the changes made by this procedure.
README file should contain:
maintenancebranch, optionally with a link to it, but make sure that link is correct if copying the
READMEfrom another module.
For examples, see the list of deprecated repositories below.