# Possible future release numbering **URL:** \ **Category:** Developers\ **Created:** [October 16, 2023, 11:39pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262 "2023-10-16T23:39:14Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![cgbab](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/cgbab/32/6133_2.png) [@cgbab](https://klipper.discourse.group/u/cgbab)\ **Post date:** [October 16, 2023, 11:39pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/1 "2023-10-16T23:39:14Z")
That makes absolutely no sense. If you go from v0.12.0, a v1 should not be 13. It’s either v0.13 or v1.0 or v1.1 ---
**Author:** ![johboh](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/johboh/32/7718_2.png) [@johboh](https://klipper.discourse.group/u/johboh)\ **Post date:** [October 24, 2023, 2:30pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/2 "2023-10-24T14:30:36Z")
Agreed, this is a nice read: [https://semver.org/](https://semver.org/) ---
**Author:** ![hcet14](https://avatars.discourse-cdn.com/v4/letter/h/ecd19e/32.png) [@hcet14](https://klipper.discourse.group/u/hcet14)\ **Post date:** [October 24, 2023, 3:34pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/3 "2023-10-24T15:34:08Z")
@johboh @cgbab > [@Upcoming v0.12.0 release](https://klipper.discourse.group/t/upcoming-v0-12-0-release/10948/1): > > The release after this one I will look to tag as “v1.13.0”. I guess it’s just a typo. Probably koconnor wanted to write: "The release after this one I will look to tag as “v0.13.0”. ---
**Author:** ![cgbab](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/cgbab/32/6133_2.png) [@cgbab](https://klipper.discourse.group/u/cgbab)\ **Post date:** [October 24, 2023, 3:45pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/4 "2023-10-24T15:45:48Z")
If it’s not, I am worried that people like this are maintaining Klipper. ---
**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\ **Post date:** [October 24, 2023, 5:44pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/5 "2023-10-24T17:44:14Z")
@cgbab Surely I must have missed it, but so far I did not see your name contributing to anything Klipper related. Please be so kind to point me to your contributions to Klipper or the OSS community in general that qualifies you to come across with such statements ---
**Author:** ![cgbab](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/cgbab/32/6133_2.png) [@cgbab](https://klipper.discourse.group/u/cgbab)\ **Post date:** [October 24, 2023, 7:37pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/6 "2023-10-24T19:37:35Z")
I may not be contributing, but I do know how a basic numbering system works. It scares me that someone is working on something that so many people depend on that does not. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [October 24, 2023, 8:13pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/7 "2023-10-24T20:13:06Z")
Obviously you see the version numbering as way more important than the software and effort behind it. BTW: > [@](#): > > Developers may choose to jump multiple minor versions at a time to indicate that significant features have been added, but are not enough to warrant incrementing a major version number; for example, [Internet Explorer 5](https://en.wikipedia.org/wiki/Internet_Explorer_5) from 5.1 to 5.5 or [Adobe Photoshop](https://en.wikipedia.org/wiki/Adobe_Photoshop) 5 to 5.5. This may be done to emphasize the value of the upgrade to the software user or, as in Adobe’s case, to represent a release halfway between major versions (although levels of sequence-based versioning are not necessarily limited to a single digit, as in [Blender](https://en.wikipedia.org/wiki/Blender_(software)) version 2.91 or _[Minecraft](https://en.wikipedia.org/wiki/Minecraft)_ Java Edition starting from 1.7.10). From: [Software versioning - Wikipedia](https://en.wikipedia.org/wiki/Software_versioning) ---
**Author:** ![mykepredko](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/mykepredko/32/2085_2.png) [@mykepredko](https://klipper.discourse.group/u/mykepredko)\ **Post date:** [October 24, 2023, 8:41pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/8 "2023-10-24T20:41:08Z")
Over the years/decades I’ve been involved with software development, I can think of quite a few cases where version label changes do not make sense or are confusing to users that are not part of the software development process - along with this marketing people often get involved and you get a mess like Windows: ![image](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/8/8eafb9b94d2cc601b945799a08789d1d53e06a09.png) Note that I used the term “label” to describe the version rather than “number” - this was to point out that the version information is basically arbitrary no matter where you go. Somebody had to first decide how to track software and set out some kind of rule for updating the version label, which is probably different from what others would come up with in a similar situation. Regardless, if the jump in the version so shakes your confidence in Klipper that you are making this big a deal of it, I suggest you don’t use Klipper. ---
**Author:** ![cgbab](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/cgbab/32/6133_2.png) [@cgbab](https://klipper.discourse.group/u/cgbab)\ **Post date:** [October 24, 2023, 9:04pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/9 "2023-10-24T21:04:02Z")
All I said was going from 0.12 to 1.13 made no sense. Everyone else was making a big deal out of it. And I was a software developer for over 40 years, and I am retired now. ---
**Author:** ![Arksine](https://avatars.discourse-cdn.com/v4/letter/a/ce7236/32.png) [@Arksine](https://klipper.discourse.group/u/Arksine)\ **Post date:** [October 26, 2023, 10:26am UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/10 "2023-10-26T10:26:21Z")
No one made a big deal out of feedback on Klipper’s versioning scheme. The concern trolling was unnecessary, we prefer to keep the discussion civil. On the topic of versioning, I have seen schemes similar to that proposed by Kevin, where the `major` number indicates significant change, the `minor` number is the overall release, and the `patch` is reserved for hotfixes. Thus `v1.13.0` would represent the first “official” stable release and the 13th release of Klipper. While I personally prefer something similar to the Semantic Versioning standard, I don’t think the above is that confusing. If necessary we could document how Klipper versioning works. ---
**Author:** ![SteveAlfa](https://avatars.discourse-cdn.com/v4/letter/s/d07c76/32.png) [@SteveAlfa](https://klipper.discourse.group/u/SteveAlfa)\ **Post date:** [October 29, 2023, 2:40am UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/11 "2023-10-29T02:40:00Z")
It’s great to see support for IDEX mirror and duplicate modes. Thank you! ---
**Author:** ![bigExtruder](https://avatars.discourse-cdn.com/v4/letter/b/94ad74/32.png) [@bigExtruder](https://klipper.discourse.group/u/bigExtruder)\ **Post date:** [October 29, 2023, 7:23am UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/12 "2023-10-29T07:23:40Z")
@cgbab sounds like you should switch to marlin. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [October 29, 2023, 7:58am UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/13 "2023-10-29T07:58:31Z")
@bigExtruder I think, the discussion is done, ok? ---
**Author:** ![leadinglights](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/leadinglights/32/4050_2.png) [@leadinglights](https://klipper.discourse.group/u/leadinglights)\ **Post date:** [October 29, 2023, 10:26am UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/14 "2023-10-29T10:26:09Z")
Indeed, this thread should get back to Kevin telling us about the upcoming release. Having said that, I am surprised that nobody took cgbab to task for saying > It’s either v0.13 or v1.0 or v1.1 This makes no sense at all: The word **either** requires only two options, not three. To paraphrase: > … I am worried that people like this are criticizing Klipper. ---
**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\ **Post date:** [October 29, 2023, 10:59am UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/15 "2023-10-29T10:59:26Z")
@leadinglights : > [@leadinglights](#): > > Indeed, this thread should get back to Kevin telling us about the upcoming release. You agree, but why do you still put oil to the fire? * * * I think this one is to be closed. ---
**Author:** ![koconnor](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@koconnor](https://klipper.discourse.group/u/koconnor)\ **Post date:** [October 29, 2023, 4:22pm UTC](https://klipper.discourse.group/t/possible-future-release-numbering/11262/16 "2023-10-29T16:22:57Z")