Maven EA vs Commercial Nexus Stable builds

[Naros]

As an open-source maintainer, I have been advocating for this specific project for a while due to its claims about speed and features that could address some of our concerns regarding memory management and buffering.

However, I was recently made aware of a separation between the EA builds published to Maven Central and the Stable builds published to your internal Nexus repository, which are only made available to commercial customers. This raises a few questions that I would like to have answered before I can even continue on this path.

1. Is there a GitHub tag that maps 1-to-1 from an EA to stable release?
2. If there is not a 1-to-1 mapping, are any final bug fixes applied only to the stable and therefore only available on the next EA iteration after-the-fact?

As I come from a world where the release process works with a series of preview releases (alpha, beta, candidate releases) and then there is a final/stable build that is released, I'm trying to understand how a project that consumes your artifacts would be able to treat your workflow as we do with other open source projects where we only update to a build that is seen as "stable" or "final" and not pre-releases.

Thanks.

[tgd]

Hi Chris, thanks for reaching out about this and for your interest in the Chronicle Queue project. I'll reach out to the email in your profile to provide more detail on this.