Bug#459427: changelog vs. NEWS handling
- To: Sean Whitton <spwhitton@spwhitton.name>
- Cc: Adrian Bunk <bunk@debian.org>, 459427@bugs.debian.org, gregor herrmann <gregoa@debian.org>, Russ Allbery <rra@debian.org>, Bill Allombert <ballombe@debian.org>, Jeremy Bicha <jbicha@debian.org>, Peter Eisentraut <peter_e@gmx.net>, Yuri D'Elia <wavexx@thregr.org>, Andrey Rahmatullin <wrar@debian.org>, Jakub Wilk <jwilk@debian.org>, Ian Jackson <ijackson@chiark.greenend.org.uk>
- Subject: Bug#459427: changelog vs. NEWS handling
- From: Bill Allombert <ballombe@debian.org>
- Date: Thu, 5 Apr 2018 10:24:41 +0200
- Message-id: <[🔎] 20180405082441.GA21198@yellowpig>
- Reply-to: Bill Allombert <ballombe@debian.org>, 459427@bugs.debian.org
- In-reply-to: <[🔎] 87fu4aer02.fsf@iris.silentflame.com>
- References: <20080106135500.4600.6929.reportbug@colt.pezone.net> <20171203162409.rwraetilou5wy2w7@jadzia.comodo.priv.at> <20080106135500.4600.6929.reportbug@colt.pezone.net> <20180227160644.GA5841@localhost> <87371lpumw.fsf@hephaestus.silentflame.com> <20080106135500.4600.6929.reportbug@colt.pezone.net> <20180310210305.GU20833@localhost> <[🔎] 87fu4aer02.fsf@iris.silentflame.com> <20080106135500.4600.6929.reportbug@colt.pezone.net>
On Wed, Apr 04, 2018 at 12:00:29PM -0700, Sean Whitton wrote:
> Hello Adrian,
>
> Thank you for your continued effort to get this bug resolved.
>
> On Sat, Mar 10 2018, Adrian Bunk wrote:
>
> >> Please expand on why you think this is the way we have to proceed.
> >
> > you skipped the part of my email with the explanation:
> >
> > with such a piecemeal approach
> > we risk fragmentation based on debhelper compat level used, with every
> > new compat level installing different files in different locations.
>
> This is not inevitable. What I am envisaging is:
>
> - we hash out our preferred solution either in this bug or in the
> debhelper bug, with the debhelper maintainer having the final say on
> what gets implemented
> - debhelper implements all of that solution at exactly one compat level
> - the archive starts to use that compat level
> - Policy is updated.
>
> This is the standard way to make changes to Policy. The alternative is
> releases of Policy rendering many packages buggy, and that is undesirable.
The standard way is to have a transition period where policy allows for both
behaviour. This way, debhelper can be updated without breaking policy
and developers would have a reference for the new behaviour.
Then the old behaviour is deprecated.
Cheers,
--
Bill. <ballombe@debian.org>
Imagine a large red swirl here.
Reply to: