Hi, I think for initial releases we should always include a link to the repo to ease getting an overview: https://github.com/apache/sling-org-apache-sling-mcp-server
IIUC the artifact generated is feature model (https://github.com/apache/sling-org-apache-sling-mcp-server/blob/master/src/main/features/main.json) and two bundles. I think it would be nice to separate those two aspects into individual sub projects and extend the readme a bit on what it takes to deploy based on the bundles. WDYT? Konrad > On 25. Mar 2026, at 14:59, Robert Munteanu <[email protected]> wrote: > > Hi, > > We solved 0 issue in this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310710&version=12356797&styleName=Text > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-3081/ > > You can use this UNIX script to download the release and verify the > signatures: > https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh > > Usage: > sh check_staged_release.sh 3081 /tmp/sling-staging > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ... > > This majority vote is open for at least 72 hours. > > Regards, > Robert Munteanu >
