Bug#1142295: debian-policy: Policy major digit should match the Debian release version

Peter Pentchev <[email protected]> Fri, 17 Jul 2026 16:49:54 +0300
Newsgroups gmane.linux.debian.devel.policy
Message-ID <aloy_Y5tQQmn4ef6__47861.679869105$1784296288$gmane$org@straylight.m.ringlet.net>
--ra4gXOK5BRYnX+zS
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 17, 2026 at 03:36:24PM +0300, Martin-=C3=89ric Racine wrote:
> pe 17.7.2026 klo 15.19 Guillem Jover ([email protected]) kirjoitti:
> > On Fri, 2026-07-17 at 15:04:00 +0300, Martin-=C3=89ric Racine wrote:
> > > Package: debian-policy
> > > Severity: wishlist
> > > X-Debbugs-Cc: [email protected]
> > >
> > > Standards-Version 4.7.4 was introduced during the development of
> > > Debian 14, but the version number doesn't reflect that.
> >
> > > Meanwhile, debhelper-compat 14 was introduced during the same develop=
ment
> > > cycle and it indeed matches the upcoming Debian release version.
> > >
> > > I propose that, from now on, Debian Policy switches to a 3-part versi=
on:
> > >
> > > x.y.z
> > >
> > > Where X denotes the Debian release (e.g. 14 for Forky) during which
> > > the policy was introduced, X denotes major changes in policy or
> > > packaging, Y denotes minor adjustments in policy or packaging.
> > >
> > > As an example, the current 4.7.4 could be renumbered to 14.7.4 to
> > > reflect the ongoing development schedule.
> >
> > The problem is that the Debian Policy and debhelper are not alike. In
> > the Debian Policy case, major changes are added whenever, regardless of
> > a specific start of a Debian release cycle. For debhelper, incompatible
> > or breaking changes get accumulated in the next compat level and then
> > released, which makes it easy to sync with a Debian release cycle, and
> > by definition all those changes will be major.
> >
> > Using the Debian release number for the Debian Policy would mean that
> > the first component would no longer imply major changes in the Policy,
> > just the time when they happened in the Debian release cycle.
>=20
> That would be the whole point. The first digit would now have a
> concrete significance. It would indicate during which Debian release
> cycle the packaging was last updated.

To reword Guillem's point, the first digit does indeed have
an extremely concrete significance right now, pretty much semver-like,
and that is really useful IMHO.

G'luck,
Peter

--=20
Peter Pentchev  [email protected] [email protected] [email protected]
PGP key:        https://www.ringlet.net/roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

--ra4gXOK5BRYnX+zS
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEELuenpRf8EkzxFcNUZR7vsCUn3xMFAmpaMv0ACgkQZR7vsCUn
3xMBEBAAlkdlM5SoXdni3ltpROlqtnt8QMedfNoHYKKQqRSxSdHs2oc1d5x2YHvA
mrnJ2UCA9PD3pCpaif/deOhlRYluRwnt4NtE4VehFFMGmt0VC+NIgQ7JmgczNs0T
VknczLCdJcWFAq1SKem5DmOX75ezSs6p+cBsBw+zeTtmOoQjBtjQbih8BG3NXzA1
cfPgMDyh5xbMUAzK2qRZoCCLdMixw6lVGSRpWBD+SN4RG30AOF3eMBIUdme6z0Ih
6eML0sIcJK558YsBnNhWGio1mWEVmE704SnAGi+VQ4CuEQW50CrV4W2ioA5NB7rz
HzLCfT/nxqfe7GgPfwIE8ZLAOJPaoAFm8FisG6jdGPdkBr/fh7LisNsEkTMKTdRt
36Y8ASODGv7U9IWhV4dkIBsL1fohlGsf+YkrZUzM+IvCb2aX8R0fCv+qCBMcjBUX
mhVT/s+9wok+tdtoG5bYTd/7WMC7ULfbByFbvqVK9V/GDbvKA6DNLcHiWW9t8onn
fFO9SM2htmDPqd5ynqginUCRS9Y2Ui8XGKgCmpQeGR7c6o3T+kbg5GyvhNARfTLu
2jv54kt32OhJ/Ozlb5MYpQExRe5/HDtkP5pu/L4DEwrkCV63vZ39PydfMJNVpcn6
TKDAFiKb1fwOAdTQDvsb6Vjtr/BuHUmbIqY3EORgSLTvIb2/LOg=
=Dd8J
-----END PGP SIGNATURE-----

--ra4gXOK5BRYnX+zS--