After months of back-and-forth with Chocolatey moderators, wrestling with my internal tooling, and overcoming several other hurdles, we will finally have a Chocolatey package for the Firebird ODBC driver v3.
Most of the difficulties stemmed from two main issues:
-
The absence of official releases published in this repository.
-
The use of a four-number versioning scheme in this project, with the fourth number representing patches.
- Today, almost everyone follows Semantic Versioning, including the main Firebird Database project.
- I had to tweak some tooling to use the fourth version number instead of the third. It worked as a quick hack, but it’s not a clean solution. Semver conventions are well established, and it’s often difficult to work around hardcoded assumptions.
Given all this, I strongly recommend that we adopt Semantic Versioning starting from version 3.1 onward.
This will simplify integration with existing automated tools and reduce friction with large ecosystems like Chocolatey and GitHub Actions.
After months of back-and-forth with Chocolatey moderators, wrestling with my internal tooling, and overcoming several other hurdles, we will finally have a Chocolatey package for the Firebird ODBC driver v3.
Most of the difficulties stemmed from two main issues:
The absence of official releases published in this repository.
The use of a four-number versioning scheme in this project, with the fourth number representing patches.
Given all this, I strongly recommend that we adopt Semantic Versioning starting from version 3.1 onward.
This will simplify integration with existing automated tools and reduce friction with large ecosystems like Chocolatey and GitHub Actions.