adityamparikh commented on PR #18:
URL: https://github.com/apache/solr-mcp/pull/18#issuecomment-3513498113
From Claude's Review: The release process in this Solr MCP repository does
not **directly** mirror the Apache Solr Docker repository, though both follow
Apache Software Foundation (ASF) requirements. Here are the key findings:
**Similarities (ASF Compliance)**
Both repositories strictly adhere to ASF release requirements:
- 72-hour minimum voting period with 3+ binding PMC votes
- Source distribution as the official release (Docker images are
"convenience binaries")
- GPG signing requirements for release artifacts
- No pre-vote publishing of Docker images
**Major Differences**
**Build System**
- Solr MCP: Uses Jib (Google's containerization plugin) - no Docker daemon
needed
- Solr Docker: Traditional Dockerfile approach built by Docker Official
Images
**Release Automation**
- Solr MCP: GitHub Actions workflows with manual triggers
(release-publish.yml)
- Solr Docker: Solr Release Wizard generates Dockerfiles, then automated
PR to docker-library
**Publishing Strategy**
- Solr MCP:
- Direct publishing to multiple registries (GHCR, Docker Hub)
- Includes MCP Registry integration
- Has dedicated nightly builds (nightly-build.yml)
- Solr Docker:
- Only Docker Hub Official Images
- Requires Docker team approval
- No nightly builds
**Dockerfile Management**
- Solr MCP: Single Dockerfile embedded in Jib configuration, can be
modified
- Solr Docker: Immutable Dockerfiles after release, generated from main
Solr repo
**Conclusion**
The Solr MCP release process appears to be inspired by ASF best practices
(which Solr Docker also follows) but is independently designed for its specific
use case as an MCP server. It's optimized for:
- Modern containerization (Jib instead of traditional Docker)
- MCP ecosystem integration
- Greater publishing flexibility
- Automated nightly builds
The documentation structure and ASF compliance suggest the team studied
Apache release requirements but created their own workflow suited to the
project's needs rather than directly mirroring Solr Docker's process.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
