[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-release-team
Subject:    Re: KDE Gear and hotfix releases, how to see whether a user has the hotfix?
From:       Rolf Eike Beer <kde () opensource ! sf-tec ! de>
Date:       2021-10-27 14:21:49
Message-ID: 2603208.mvXUDI8C0e () eto ! sf-tec ! de
[Download RAW message or body]

Am Montag, 25. Oktober 2021, 22:50:22 CEST schrieb Heiko Becker:
> On Monday, 25 October 2021 01:57:58 CEST, Friedrich W. H. Kossebau wrote:
> > CAN WE HAVE KDE GEAR DO INDIVIDUAL AND VERSIONED HOTFIX RELEASES?
> > 
> > So ideally KDE Gear has an option to do intermediate hotfix releases of
> > individual software as well, with proper identifier in the version.
> > 
> > Two challenges I see:
> > a) a simple way to run the KDE Gear scripts for an individual package
> 
> There is, to some degree, at least to create a single tarball. That's how
> respins are handled.
> 
> > b) have an extended KDE Gear version scheme, to be able to denote any
> > additional hotfix releases (e.g. for tag, package name, UI version
> > strings).
> I haven't actually looked and tested if any of the tooling would break with
> the next scheduled release, but assuming the version is changed manually
> for the hotfix release, I don't see why we couldn't have yy.mm.[0-3]a (and
> b, c,..) if needed.

Given the nightmare these non-digit versions components can be (anyone 
remember OpenSSL 1.0.2za?) I would very much welcome it being called .1 
instead of a, e.g. 2021.08.3.1.

Eike


[prev in list] [next in list] [prev in thread] [next in thread]