Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/cmake: bump version to 3.15.5
Date: Sat, 2 Nov 2019 22:31:51 +0100	[thread overview]
Message-ID: <20191102223151.115b219b@windsurf.home> (raw)
In-Reply-To: <20191102102425.GA2710@scaer>

On Sat, 2 Nov 2019 11:24:25 +0100
"Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> On 2019-11-01 22:40 +0100, Bernd Kuhls spake thusly:
> > Release notes:
> > https://blog.kitware.com/cmake-3-15-5-available-for-download/  
> 
> Thanks for the poitner to the release notes.
> 
> Although I understand we usually want to update, the release notes for
> this version only list one fix to an example file, and fixes for VS
> (Visual Studio, thus Windows) and Xcode (thus MacOS). So, nothing that
> applies to Linux, and to us.
> 
> I don't think we want updates just for the sake of having updates.
> Bumping a package, especially one that can be considered part of the
> core components, should bring something besides just bragging about
> "up-to-date".

I beg to disagree here. Of course, in stable releases or after -rc1 has
been released, we don't want to see "gratuitous" version bumps.

However, outside of these moments, those gratuitous updates are fine.
Indeed, they reduce the effort that will be needed for the next "real"
bump. Indeed, we can very easily check what are the changes between
3.15.4 and 3.15.5, but what if we don't update to 3.15.7, 3.15.8,
3.15.9 because none of these contain any change that look "useful" ?
Then when 3.15.10 appears, we have to bump from 3.15.4 to 3.15.10 in
one go, and review at this point what all the changes were. I very much
prefer doing incremental bumps.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-11-02 21:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01 21:40 [Buildroot] [PATCH 1/1] package/cmake: bump version to 3.15.5 Bernd Kuhls
2019-11-02  9:08 ` Thomas Petazzoni
2019-11-02 10:24 ` Yann E. MORIN
2019-11-02 21:31   ` Thomas Petazzoni [this message]
2019-11-03  9:29     ` Yann E. MORIN

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=20191102223151.115b219b@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox