Opened 7 years ago
Last modified 10 months ago
#16870 closed enhancement
JOSM versioning — at Initial Version
| Reported by: | michael2402 | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | hack-weekend-2018-10 | Cc: |
Description
Currently, JOSM is versioned by it's SVN revision.
In the future, we want to version JOSM without relying on the JOSM version. For this, there will be two versioning schemes:
For tested versions, there will be a version of:
<year>.<month>.0
If we do tested releases for quickfixes (multiple tested per month), we use
<year>.<month>.1, <year>.<month>.2, ...
For latest version, we use:
<year>.<month>.<last tested minor + 1>-SNAPSHOT-<date>
e.g.: 18.11.1-SNAPSHOT-201811181423
We will have a build task to do the next development iteration (tag + update version)
For @since tags, we will keep them as @since xxx in source and run the replacement as soon as we do a release and then tag them with the official release version. We don't know the exact snapshot version when adding the @since tags, but since we often use branches there is no way of determining them.
Plugins can use the SNAPSHOT version to specify that they rely on an experimental version.
