nebula-plugins / nebula-plugins/nebula-release-plugin
Feature to create 'Release Candidate' based on given base release version.
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 236
- Forks
- 60
- Avg merge
- 10m
- Merged PRs (30d)
- 4
Description
If I create release tag 1.0.0 then, 'gradle candidate' will create ' v1.1.0-rc.1' and so on...
then, If I create release tag 2.0.0 then, 'gradle candidate' will create ' v2.1.0-rc.1' and so on...
But, it would be better to have a feature like, to create release candidates based on given release versions.
Eg:-
'gradle -Prelease.version=1.0.0 candidate' will create next candidate version like, ' v1.1.0-rc.4'
'gradle -Prelease.version=2.0.0 candidate' will create next candidate version like, ' v2.1.0-rc.10'
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
Start by tracing the existing candidate Gradle task and how it determines the base release version and candidate number. Use the examples in the issue to verify that -Prelease.version=1.0.0 and -Prelease.version=2.0.0 select the corresponding candidate sequence; done means both commands create the requested next versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- groovy
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100