jMonkeyEngine / jMonkeyEngine/sdk
Update Center: Versioning
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 348
- Forks
- 104
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
We need to come up with a versioning scheme, specifically for nightlies, where we can't manually bump the version.
The problem is that the current version always is 3.3.0.1 and the installed SDK always has 3.3.0.0, causing nightlies update to only be available once I guess and also downloading all modules, even if they remain unchanged.
Maybe some git extract magic? We could get the commit difference since the last tag or something, but using that to hand out different versions for every module might not work/break.
Contributor guide
No contributing guide indexed for this repository
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 files, tests, or entry points are mentioned. Start by locating where the nightly version 3.3.0.1 and installed SDK version 3.3.0.0 are generated, then trace how module versions control update downloads. Done means a versioning scheme distinguishes successive nightlies and prevents unchanged modules from being downloaded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100