This is an automated email from the ASF dual-hosted git repository. reschke pushed a commit to branch reschke-patch-3 in repository https://gitbox.apache.org/repos/asf/sling-site.git
commit 1fff979ddcd86c8f9dd9c2c196cda554d1965300 Author: Julian Reschke <[email protected]> AuthorDate: Tue Aug 18 15:37:07 2026 +0200 Update staging repository link in release management doc --- src/main/jbake/content/documentation/development/release-management.md | 2 +- 1 file changed, 1 insertion(+), 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 a78a2f9bc..14c668b61 100644 --- a/src/main/jbake/content/documentation/development/release-management.md +++ b/src/main/jbake/content/documentation/development/release-management.md @@ -182,7 +182,7 @@ First prepare your POMs for release: * You can continue to use `mvn release:prepare` and `mvn release:perform` on other sub-projects as necessary on the same machine and they will be combined in the same staging repository - this is useful when making a release of multiple Sling modules. 1. Close the staging repository: - * Login to [https://repository.apache.org](https://repository.apache.org) using your Apache credentials. Click on *Staging Repositories* on the left. Then click on *org.apache.sling* in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select *Close*. This will close the repository from future deployments and make it available for others to view. If you are staging multiple release [...] + * Login to [https://repository.apache.org](https://repository.apache.org/#stagingRepositories) using your Apache credentials. Click on *Staging Repositories* on the left. Then click on *org.apache.sling* in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select *Close*. This will close the repository from future deployments and make it available for others to view. If you are sta [...] 1. Verify the staged artifacts * If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of \*.asc (signature) files. If you don't like the content of the repository, right click your repository and choose *Drop*. You can then redo (see [Redoing release perform](#redoing-release-perform)) or rollback your release (see *Canceling the Release*) and repeat the process
