id summary reporter owner description type status priority milestone component version resolution keywords cc 16870 JOSM versioning michael2402 team "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: `.` If we do tested releases for quickfixes (multiple tested per month), we use `..1`, `..2`, ... For latest version, we use: `..-SNAPSHOT` (e.g. `18.11.1-SNAPSHOT`) to describe the current latest snapshot for the given year, month and quickfix. When publishing snapshots, the string `SNAPSHOT` is replaced by a unique identifier (e.g.: `18.11.1-20181118.142301-42`). 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." enhancement new normal Core hack-weekend-2018-10