konveyor / konveyor/java-analyzer-bundle
Proper handling of project versioning for new releases
- Dominant language
- Java
- Stars
- 2
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
There is no updating of versions in the maven project pom files for new releases at the moment, see sample here :
https://github.com/konveyor/java-analyzer-bundle/blob/v0.3.0-alpha.2/pom.xml#L8
Also the versions of these artifacts do not seem aligned with konveyor versioning , at the moment they are 1.0.0
The SNAPSHOT versioning in maven is a moving pointer meant for development purposes , proper lifecycle procedures to version the artifacts correctly should be implemented at least for official final releases
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the Maven pom.xml files, including the version shown in the v0.3.0-alpha.2 example, and compare their artifact versions with the Konveyor release version. Trace the current release process before deciding how versions should be updated. Done means official final releases use aligned, non-SNAPSHOT artifact versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100