Hi Peter, On Sat, 10 Apr 2021 10:14:31 +0200, Peter Korsgaard wrote: > >>>>> "Wolfram" == Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx> writes: > > >> We don't usually do minor version updates for bug fixes. Instead, what > >> I do is maintain a list of such "must have" fixes, that package > >> maintainers can refer to. Look for "Recommended patches" at: > >> > >> https://i2c.wiki.kernel.org/index.php/I2C_Tools > >> > >> There's no section for version 4.2 yet, but we can add one as soon as > >> the commit hits the public repository. > > > I added a section now for the 4.2 release. And (finally!) started > > cleaning up the wiki a little. > > Thanks! As a packager, I must say that this way of handling bugfixes > isn't great - I only just noticed this now by accident. > > What is the issue with making bugfix releases? The main issue is that making releases (bugfix or not) takes time. Even though it's partly automated, there are still a number of manual steps involved, and you can't afford getting them wrong. So as far as I am concerned, making a release is always a time of stress. Making a bugfix release would also require a change in my process, as we would need a new branch in git to cherry pick the fixes that need to go into the bugfix release. Second issue is that I chose to go for 2-number versions for i2c tools v4. Doing bugfix releases with 3 numbers now means mixing 2-number versions with 3-number versions which can lead to confusion (for sorting order, if nothing else). Maybe I should have gone for 3-number versions, but as I did not have the intention to make bugfix releases in the first place, this seemed overkill. And I still think it is, as I believe - if memory serves - it is the first time we face a regression in i2c-tools since I started managing the project. i2c-tools is a small project with few commits, I simply don't want to make the process around it more complex than needed. I must say I'm surprised to see requests for more frequent and/or bugfix releases when the world has moved to CD/CI and some projects have abandoned the very notion of version number. If you can't be bothered with checking the recommended fixes on top of the latest release, then maybe just use the latest git snapshot always? -- Jean Delvare SUSE L3 Support
