| ▲ | rolymath 8 hours ago | |
The Python community loves confusing versioning. I mean, obviously Python 2.7 is newer than Python 3.1 I remember swearing I would never migrate to python3 but here we are, I migrated without even feeling it or realizing when (But I do remember django played a big role). | ||
| ▲ | chme 8 hours ago | parent | next [-] | |
That isn't confusing at all, if you know how maintained stable releases work. Happens with the Linux kernel as well. | ||
| ▲ | hk__2 7 hours ago | parent | prev | next [-] | |
There are a lot of large projects where X.1 is newer than Y.0. You release a new major version for breaking changes, but you backport security changes to previous major releases as well. | ||
| ▲ | jubilanti 6 hours ago | parent | prev | next [-] | |
Just read https://semver.org/ | ||
| ▲ | Longwelwind 8 hours ago | parent | prev | next [-] | |
Isn't that whole point of semantic release? Minors and hotfixes allow you to release a new version for an older release (like if you released 3.7 but you found a bug present in 3.4, you can release 3.4.1 which would be newer than 3.7), making it possible to have multiple supported versions at the same time. | ||
| ▲ | yard2010 8 hours ago | parent | prev | next [-] | |
Tangibly related, did you know that odd versions of node don't get LTS, I found it odd at first | ||
| ▲ | paulddraper 7 hours ago | parent | prev [-] | |
That’s probably the worst example you could have chosen. You shouldn’t assume anything about relative date of 2.7 and 3.1. | ||