development pmc deprecation github

Deprecating Sling Modules

The following procedure is recommended to deprecate Sling Git repositories, indicating that they should no longer be used.

  • Get consensus on our dev list or do a PMC vote, depending on the importance of the module
  • Create a branch named maintenance with the last version before deprecation.
  • Empty the master branch, keeping just README.md, LICENSE,.gitignore and .asf.yaml files.
  • Add the deprecated GitHub topic to the module, using a .asf.yaml file in the master branch.

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 contents for deprecated repositories

The README file should contain:

  • The Sling logo.
  • A link to sling.apache.org.
  • The module name with the (deprecated) mention.
  • A link to the replacement module(s) if any.
  • A mention of the maintenance branch, optionally with a link to it, but make sure that link is correct if copying the README from another module.

For examples, see the list of deprecated repositories below.

Others tasks

  1. Update the list of Sling modules (default.xml) in Sling Aggregator, as the project labels now contain the deprecated hint.
  2. Move module to the "Deprecated" group in the Sling Site Download List, downloads.tpl
  3. Set unreleased versions for this module from JIRA Releases to "Archived"

See Also

- ( Deprecating Sling Modules )