Hello Solr Engineers,

For adding First Party MCP Support
https://issues.apache.org/jira/browse/SOLR-17944
we created https://github.com/apache/solr-mcp and would like to onboard it
to the Apache Trusted Releases (ATR) process as per Jan's recommendation
here https://github.com/apache/solr-mcp/pull/18#discussion_r2511975722

I created Jira ticket for the Apache Infrastructure team
https://issues.apache.org/jira/browse/INFRA-27404

This project will meet the requirements listed in
https://infra.apache.org/release-signing.html#automated-release-signing


   - All artifacts being signed can be built reproducibly
   <https://reproducible-builds.org/> -

*Project uses gradle build tool using gradle wrapper so the version of
   gradle this project will build with is downloaded. Hence the jar produced
   is reproducible and so is the docker image produced using the jib gradle
   plugin.   *
   - CI deploys the artifacts to a staging environment -

*Project uses GitHub actions publishes nightly builds via
   
https://github.com/apache/solr-mcp/pull/18/files#diff-2ee59052448a421cff47b6ee98f786b57f3012d9f9132d37b9bde685a6266166
   
<https://github.com/apache/solr-mcp/pull/18/files#diff-2ee59052448a421cff47b6ee98f786b57f3012d9f9132d37b9bde685a6266166>
   to apache/solr-mcp-nightly on Docker Hub requiring credentials. It also
   needs a location to upload the tarball. *
   - The release procedure contains a validation step where all artifacts
   are reproduced on trusted hardware
   <https://www.apache.org/legal/release-policy.html#owned-controlled-hardware>
before
   publication to pages intended for end users - *Through GitHub actions,
   the code is checked out on a fresh virtual machine provisioned by GitHub. *

   Put together a dev-docs/WORKFLOWS.md

   
https://github.com/apache/solr-mcp/pull/18/files#diff-b3f909aba11a9441c240087a7c2f8a4c4ba4d9ad646ad6f44c02433924e2736d
   which goes over which workflow to use when.


   
https://github.com/apache/solr-mcp/pull/18/files#diff-d437dc518eea2891a06d511dd4902d4e21a35b72dff8b1212329f358aff6c04c
   is the action for ATR which requires ASF_USERNAME of release manager and
   manually send out drafted emails. This file will change in accordance with
   onboarding to ATR is completed.

   Please add your comments/concerns/suggestions.

-- 
Thanks,
Aditya

Reply via email to