From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Sat, 2 Nov 2019 22:31:51 +0100 Subject: [Buildroot] [PATCH 1/1] package/cmake: bump version to 3.15.5 In-Reply-To: <20191102102425.GA2710@scaer> References: <20191101214052.19167-1-bernd.kuhls@t-online.de> <20191102102425.GA2710@scaer> Message-ID: <20191102223151.115b219b@windsurf.home> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net On Sat, 2 Nov 2019 11:24:25 +0100 "Yann E. MORIN" 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