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

rombert 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 eab394ea4 SLING-8307 - Update the Eclipse tooling release process 
after the restructuring and code signing changes
eab394ea4 is described below

commit eab394ea4240c9d31d1e8f04c5227f8677a67f17
Author: Robert Munteanu <romb...@apache.org>
AuthorDate: Thu Sep 25 13:35:12 2025 +0200

    SLING-8307 - Update the Eclipse tooling release process after the 
restructuring and code signing changes
    
    Clarify Eclipse Marketplace listing update
---
 src/main/jbake/content/documentation/development/release-management.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git 
a/src/main/jbake/content/documentation/development/release-management.md 
b/src/main/jbake/content/documentation/development/release-management.md
index c5b57c914..6ebd2fc2d 100644
--- a/src/main/jbake/content/documentation/development/release-management.md
+++ b/src/main/jbake/content/documentation/development/release-management.md
@@ -345,7 +345,8 @@ Once the release has passed, the following must be done:
 1. remove the old update site from 
https://dist.apache.org/repos/dist/release/sling/eclipse/1.2.2/ versions but 
leave pointers to archive.apache.org, using 
compositeArtifacts.xml/compositeContent.xml , with a single child entry 
pointing to https://archive.apache.org/dist/sling/eclipse/1.2.2/
 1. remove the staged artifacts from 
https://dist.apache.org/repos/dist/dev/sling/ide-tooling-1.3.0
 1. update the news page and the download pages
-1. update the Eclipse Marketplace listing
+1. update the [Eclipse Marketplace 
listing](https://marketplace.eclipse.org/content/sling-ide-tooling)
+    1. we do not maintain multiple 'solution versions' so just update the 
version and make sure that supported Eclipse releases and minimum Java version 
are correct
 
 ## Appendix A: Creating and registering your PGP key
 

Reply via email to