Replies: 2 comments 2 replies
-
One idea I have is to make the master branch the latest tag for containers. So if someone pulls ghcr.io/cyclonedx/cdxgen they get the master branch. Should they prefer stability, they can refer to a specific tag or sha |
Beta Was this translation helpful? Give feedback.
2 replies
-
Second idea. Don't make any releases until a few people test and confirms that the master branch is ready to be released. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Everyone wants a stable and well-tested cdxgen. The master branch on both the container and the repo almost sees no downloads, which means 100% of the testing effort falls into the hands of the maintainers.
We often have no idea about regression bugs, so don't know if the master branch is even ready to be released. Most successful open-source projects would have a combination of users on both rolling and stable releases.
What's the best way to encourage the community to start testing the master branch in non-production environment and submit any regression bugs (performance and functional)?
Beta Was this translation helpful? Give feedback.
All reactions