Timeline for Why did CPLEX jump from version 12 to version 20?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2021 at 9:30 | comment | added | Geoffrey De Smet | Yes, that's common. Although I'd argue it's not all marketing people. Only marketing and engineering that think short-term. Then you get situations like "Windows 95 is older than Windows 10". Or Weblogic 8.1, which skipped Weblogic 8.0 because their users didn't buy ".0" versions. | |
| Apr 9, 2021 at 20:42 | comment | added | prubin♦ | From a technological standpoint, I would agree. Note, though, that the Apache guidelines seem to have been developed for libraries rather than commercial products. I suspect the marketing people for the latter want the major version ticking upward periodically to keep the product looking "current", "state of the art" or whatever. | |
| Apr 9, 2021 at 8:32 | comment | added | Geoffrey De Smet | Why can't everyone just stick with Apache version guildelines? MAJOR.MINOR.HOTFIX: if the MAJOR version changes, it breaks backwards compatibility. If the MINOR version changes, features are added. If the HOTFIX version changes, it fixes bugs. That's simple, clear and reliable. | |
| Apr 2, 2021 at 20:39 | vote | accept | Matthias Fripp | ||
| Apr 2, 2021 at 15:54 | history | answered | prubin♦ | CC BY-SA 4.0 |