Jan Engelhardt schrieb:
A better example would be systemd, which jumped from 44 to 183 because it synced with udev. The version bump was not involved in making systemd/udev a success, and since openSUSE cannot even bring the synchronization argument, that's the result.
When I was studying physics, one professor of Theoretical Physics had this sentence that he brought up again and again - "The coordinate system is both necessary and irrelevant at the same time." (It's necessary for creating mathematical descriptions, but it's not existent in nature and you can define it however you want, so it has to be scientifically irrelevant.) A few years ago, in the big discussions about the new Firefox versioning scheme, I realized the same is true for version "numbers" in software - they are both necessary and irrelevant. Necessary for orientation, to know by comparison if what you have is current, to know if what we talk about is the same state of code. Irrelevant as you can define your versioning scheme however you want. Doing 0.x forever, arbitrarily bump the major number when you feel like it (like the Linux kernel now), bump the major every development cycle (like Firefox), asymptotically nearing e or pi, having some large gaps, using 1 to 4 groups of digits, using years and months or plain numbers or even letters, start with 0 or 1, etc. - and that's all still within the boundaries of the common schemes - you can of course go even orthodox if you like, as long as there's some way to understand it. In the end, I found it healthy to think about it that way, removes a lot of "but this is wrong" (as there is no right or wrong - remember, they're as irrelevant as necessary) and replaces it with "is it useful, can we work with this reasonably?" instead. KaiRo -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org