Elias Nogueira 🇧🇷🇳🇱
@eliasnogueira.com
Java Champion | Senior Principal Software Engineer | Speaker | Writer | Oracle ACE | Java Magazine NL | OSS
Reposted by Elias Nogueira 🇧🇷🇳🇱
No, because if I have a library that is feature complete, this would force me to create a release per year, because people will think the library is outdated. One of my customers uses that to force his customers to update to the newest version.
July 30, 2025 at 11:39 AM
No, because if I have a library that is feature complete, this would force me to create a release per year, because people will think the library is outdated. One of my customers uses that to force his customers to update to the newest version.
Reposted by Elias Nogueira 🇧🇷🇳🇱
I like CalVer whenever versions become a point of discussion; it's hard to argue to continue to use 2019.08 today, whereas 1.5 hides that nuance of using outdated technology.
Breaking changes with SemVer are a solved problem when you use the right technology! ;)
Breaking changes with SemVer are a solved problem when you use the right technology! ;)
July 30, 2025 at 10:59 AM
I like CalVer whenever versions become a point of discussion; it's hard to argue to continue to use 2019.08 today, whereas 1.5 hides that nuance of using outdated technology.
Breaking changes with SemVer are a solved problem when you use the right technology! ;)
Breaking changes with SemVer are a solved problem when you use the right technology! ;)
You got me in the "grab a classical concert ticket in one of the churches". Thank you!
July 23, 2025 at 8:23 PM
You got me in the "grab a classical concert ticket in one of the churches". Thank you!