[sling-site] branch master updated: Mention the need for consensus

[bd...@apache.org]

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

bdelacretaz 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 19845ae  Mention the need for consensus
19845ae is described below

commit 19845aef5ff0ff6485de7df551a3b01917e6d6cb
Author: Bertrand Delacretaz <bd...@apache.org>
AuthorDate: Tue Mar 31 11:24:22 2020 +0200

    Mention the need for consensus
---
 .../jbake/content/documentation/development/deprecating-sling-modules.md | 1 +
 1 file changed, 1 insertion(+)

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 bd7a887..5644ce5 100644
--- a/src/main/jbake/content/documentation/development/deprecating-sling-modules.md
+++ b/src/main/jbake/content/documentation/development/deprecating-sling-modules.md
@@ -8,6 +8,7 @@ tags=development,pmc,deprecation,github
 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` file.
  * 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.