Hi all, I've been working with Aditya on getting Solr MCP ready for a release. We believe that it's time for a 1.0, and that there isn't anything substantial missing that would prevent the process from moving forward. I'm looking for some feedback from the community to make sure we have consensus. A couple of questions/comments for input:1) Do we need to have an established changelog for 1.0 release? If so, would a CHANGELOG.md be sufficient for now? Can we also just build it from our Git Commit history?2) We know we need to distribute the src files, we're working on adding a gradle task for that.3) Anything special about the fact that we produce an "uberjar" that we need to know about? We would I think produce a solr-mcp-0.0.2-SNAPSHOT-plain.jar that is just the jar, and then solr-mcp-0.0.2-SNAPSHOT.jar which is the uber jar.3) Currently we have a Docker image that we build. I have never built or published a Docker image for an apache project. Do we absolutely need that for 1.0, or can we just ship the Jar file approach for now?
Unless someone else wants to volunteer to be the Release Manager, I think I am signing up for it, though I've never done it before, and I'll need handholiding. My thought is to use the new ATR process to manage all the plumbing of the release (emails, voting etc), but build and sign the artifacts locally on my laptop, and skip trying to get the Github based reproducible builds approach for 1.0. Thoughts? Eric
