Semantic versioning including patch for all releases? #12436
-
Would you mind creating all releases with a patch number? E.g. 10.4.0 instead of 10.4? I'm not sure if the checkstyle project follows SemVer (which does require 3 part version numbers). The practical reason for asking is that it's just harder to upgrade dependencies if you have to remember which ones are 3 part versions and which are 2 part versions (and the majority of stuff in maven is 3 parts also for x.y releases). Trust me, I have experienced it multiple times that I changed a version number for checkstyle in my own poms from something like X.Y.Z to X.Y+1.0, just to see the build fail, and then to remember it doesn't have the zero there. You would make my life (and that of many others) a tiny bit more simple by always going with 3 version parts. :) |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
https://checkstyle.org/#Development_Cycle
There is a discussion on this somewhere, I don't know if there has been an outcome yet. |
Beta Was this translation helpful? Give feedback.
-
version is changed to 3 digits, will always be 3 digits. |
Beta Was this translation helpful? Give feedback.
version is changed to 3 digits, will always be 3 digits.
10.5.0 - will be released on 27 Nov 2022