[sling-site] branch master updated: Recommend updating to newest parent (#69)

[kw...@apache.org]

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

kwin 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 81fd513  Recommend updating to newest parent (#69)
81fd513 is described below

commit 81fd513e25d5fe5e1894f38074706a019482b77d
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Tue Sep 21 17:27:39 2021 +0200

    Recommend updating to newest parent (#69)
    
    https://lists.apache.org/thread.html/r048cd6e689117a4fdc11e46b3b2ed834e879125d7f83c80bc60ba892%40%3Cdev.sling.apache.org%3E
---
 src/main/jbake/content/documentation/development/release-management.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index d32e6ec..8a1cd8a 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -15,6 +15,7 @@ Most of the hard work of preparing and deploying the release is done by Maven.
 ## Prerequisites
 
 * To prepare or perform a release you *MUST BE* at least be an Apache Sling Committer.
+* Try to update to the most recent parent release prior to doing a release
 * Each release must be signed, see _Appendix A_ below about creating and registering your key.
 * Make sure you have all [Apache servers](http://maven.apache.org/developers/committer-settings.html) defined in your `settings.xml`
 * See Appendix B for Maven and SCM credentials