(sling-site) branch master updated: SLING-12523 Deprecate Sling Module Process - Keep README files

[ss...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

sseifert pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 26e52de5f SLING-12523 Deprecate Sling Module Process - Keep README files
26e52de5f is described below

commit 26e52de5f8079f6b6944b7fe20fbf75d63945526
Author: Stefan Seifert <st...@users.noreply.github.com>
AuthorDate: Fri Dec 6 17:47:42 2024 +0100

    SLING-12523 Deprecate Sling Module Process - Keep README files
---
 .../content/documentation/development/deprecating-sling-modules.md    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/main/jbake/content/documentation/development/deprecating-sling-modules.md b/src/main/jbake/content/documentation/development/deprecating-sling-modules.md
index 2620b2bd3..6c00936e6 100644
--- a/src/main/jbake/content/documentation/development/deprecating-sling-modules.md
+++ b/src/main/jbake/content/documentation/development/deprecating-sling-modules.md
@@ -10,9 +10,9 @@ 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` file.
+ * 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](https://cwiki.apache.org/confluence/display/INFRA/.asf.yaml+features+for+git+repositories) 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