nebula-plugins / nebula-plugins/nebula-release-plugin
How to handle pre-rc development preview builds?
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
We're releasing a preview build so I was looking for support for 4.0.0-beta1 or something similar. dev isn't good enough because 4.0.0-dev# implies it's development after 4.0.0 landed. rc isn't enough either because these are not release candidates. These are preview versions that will take user feedback and continue development.
What's the recommend approach for this? I would prefer to have a dev commits on top as well, so 4.0.0-beta1-dev#. It seems like snapshot might be the only approach but that's too generic for our needs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is identified in the issue. Start by reviewing the plugin's existing version-qualifier handling and related release tests, then determine the supported pre-release and development-version behavior; done means the approach is agreed and its expected versioning behavior is covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100