On Tue, Nov 19, 2024 at 9:56 AM Vahila <[email protected]> wrote:
> Thank you for sharing the additional links and your inputs. I want to > confirm that based on my understanding Semantic Versioning helps indicate > the type of changes in a release(from user perspective - in case of option > two of version format), but unique identification of release artifacts > mainly relies on the machine generated changelist. > There's support for a user-controlled prefix of the version number which you can use to approximate semver. This is generally discouraged though, it's very easy to get this wrong. IMO semver for plugins also suffers from not adequately modeling how "big" of a change something is. Major new features are more relevant to me as a user than a signature change in most cases. To mark a release as incompatible with prior versions and make that information appear in the plugin manager, Jenkins uses a different mechanism (look for hpi.compatibleSinceVersion). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKWEKgNZBom36S5eo-vZUy1V25AWn0RfXcWFv%3DtuadKWw%40mail.gmail.com.
