Linux-i2c Archive on lore.kernel.org
 help / color / Atom feed
From: Jean Delvare <jdelvare@suse.de>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH i2c-tools] Revert "tools: i2ctransfer: add check for returned length from driver"
Date: Fri, 21 May 2021 13:16:00 +0200
Message-ID: <20210521131600.416c5ca7@endymion> (raw)
In-Reply-To: <87tuoe5zfc.fsf@dell.be.48ers.dk>

Hi Peter,

On Sat, 10 Apr 2021 10:14:31 +0200, Peter Korsgaard wrote:
> >>>>> "Wolfram" == Wolfram Sang <wsa+renesas@sang-engineering.com> 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

  parent reply index

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09 11:05 Wolfram Sang
2021-02-26 16:43 ` Jean Delvare
2021-03-10 20:46   ` Wolfram Sang
2021-04-10  8:14     ` Peter Korsgaard
2021-04-13 12:54       ` Wolfram Sang
2021-04-21 20:01         ` Peter Korsgaard
2021-05-21 11:21         ` Jean Delvare
2021-05-25 20:36           ` Wolfram Sang
2021-06-02  9:03             ` Jean Delvare
2021-06-02 16:25               ` Wolfram Sang
2021-06-04 13:57                 ` Jean Delvare
2021-06-04 19:21                   ` Wolfram Sang
2021-06-08 12:22                     ` Jean Delvare
2021-06-08 12:26                       ` Wolfram Sang
2021-05-21 11:16       ` Jean Delvare [this message]
2021-03-07  5:42 ` Wolfram Sang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210521131600.416c5ca7@endymion \
    --to=jdelvare@suse.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=peter@korsgaard.com \
    --cc=wsa+renesas@sang-engineering.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-i2c Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-i2c/0 linux-i2c/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-i2c linux-i2c/ https://lore.kernel.org/linux-i2c \
		linux-i2c@vger.kernel.org
	public-inbox-index linux-i2c

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-i2c


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git