From kde-release-team Fri Oct 21 13:41:30 2022 From: Heiko Becker Date: Fri, 21 Oct 2022 13:41:30 +0000 To: kde-release-team Subject: Re: releases driven through =?iso-8859-1?Q?invent=3F?= Message-Id: <559dd7a4-2755-4e82-9740-3f94636d666d () kde ! org> X-MARC-Message: https://marc.info/?l=kde-release-team&m=166635933710174 On Friday, 21 October 2022 11:44:12 CEST, Harald Sitter wrote: > On Fri, Oct 21, 2022 at 10:52 AM Antonio Rojas wrote= : >> Hi, >> ... > > plasma-workspace-1.0.0.25.tar.xz > plasma-desktop-1.0.0.0.tar.xz > >> Having each project tarball have a different version number at=20 >> release time would make it a packaging hell. > > How so? You need only ever pick the highest version number. Wearing my distro packager hat, I can understand the concerns because to=20 pick the highest version you obviously need to know it. For one package=20 this is not that much of a problem, but for example for >=3D 200 packages=20 released with Gear it can be. Furthermore I'm a little concerned that the same last digit can stand for a=20= "private" and public release as well, just depending on the unrelated fact=20= if a respin was needed or not. I assume using something like -rcN, like=20 Frameworks currently do, is not that attractive because after the testing=20 phase all final tarballs need to be created, even if they are identical to=20= the last -rc, right?