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

Andrey Rakhmatullin <[email protected]> Fri, 17 Jul 2026 17:55:14 +0500
Newsgroups gmane.linux.debian.devel.policy
Message-ID <alomMuFlM-xHVWEu__37485.4409646773$1784293049$gmane$org@belkar.wrar.name>
--6E45iMWpDeCv+3TZ
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 17, 2026 at 03:36:24PM +0300, Martin-=C3=89ric Racine wrote:
>> 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.
>
>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.

I think this detail is even less useful than Standards-Version itself as=20
it currently exists. Which problems will this solve?

--=20
WBR, wRAR

--6E45iMWpDeCv+3TZ
Content-Type: application/pgp-signature; name=signature.asc

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

iQJhBAABCgBLFiEEtf6ieDcfC1EgtGkao+OWn23e7IYFAmpaJjItFIAAAAAAFQAP
cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEKPjlp9t3uyG
HZ8P+wWE5GDgNGK8CbiIDFs92HjUjWf/z0SFGZRsFbb90Qitf6xhQfGcVqd8c8lN
BLGyJV4/yVUl0gQQdm3DAghC+Zx5Rku0C7cv+K3nLt75IwKXwhrt183R0CvGaJvh
kw1ePnc2ZkESXuc2oxCRDyeFWfZ0MbBTkSrMs343miUZ0n76vOctzeoLv0MGE4yY
y3EZEqUS/+W869blRM9ZWQ5SY6zjIFoQO4NPDMSDDnJkO6+wu6eH7qM65bN3SG24
T0kqEXoM+RAvoPMSl7/Za6mnecwJ9xOCgORwKPB9pVDQVd3uuvMn0WWr0tqT7F+h
kmxm8A0PioeaDbUDRNvuIh8p7hNf5RdIROU8faHgwRvIIsnImF8sQ4m06Rt7pG//
C1KyKgc9D0BazhHD8yXEC5gjE/O0mHRzrvN8E54PMA4KI2mLhALXvTOlRnds2Ng+
+Ha8Teyo1BRVytMHFd9vE1bL/+ISlXYhI1fXppATW8li1C3AIvkD2Ur31cT/0OIg
NVqEZmpBOkJSfxZtt8M3ECy/4qZoCXiCHokXjLs3AT0j0OyvNkNa8nsqLtKJ+/8d
C8IziVHkVFqadiKYlfSGsaeNK6TweHD23ICsWNi6dIB26g8qGldXR0PkKo2FAjU/
roXEjXW8Ga6wn0kM4KVnHblJnkkMhMSB8LK31P0ShbbT6lHz
=qZBM
-----END PGP SIGNATURE-----

--6E45iMWpDeCv+3TZ--