[sling-site] branch master updated: remove obsolete introduction

[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 4f8af3480 remove obsolete introduction
4f8af3480 is described below

commit 4f8af3480230f13a8203dd5ae20d6f8d0e70937c
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Wed Sep 21 15:58:22 2022 +0200

    remove obsolete introduction
---
 .../jbake/content/documentation/development/release-management.md   | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/src/main/jbake/content/documentation/development/release-management.md b/src/main/jbake/content/documentation/development/release-management.md
index 640e6c3a2..4d79130d4 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -4,14 +4,8 @@ status=published
 tags=development,pmc
 ~~~~~~
 
-Sling releases (and SNAPSHOTS) are deployed to the [Nexus repository](http://repository.apache.org) instead of the traditional deployment via the Maven 2 mirrors source on `people.apache.org`. This makes the release process much leaner and simpler. In addtion we can benefit from the Apache Parent POM 6, which has most of the release profile setup built-in.
-
-Most of the hard work of preparing and deploying the release is done by Maven.
-
 [TOC]
 
-
-
 ## Prerequisites
 
 * To prepare or perform a release you *MUST BE* at least be an Apache Sling Committer.