Policy proposal: Consistent use of UNRELEASED in debian/changelog
Hi! I am proposing a minor addition to the DPT policy to try to make the use of UNRELEASED in debian/changelog more consistent. The full diff can be found here [1]. The problem this tries to solves is inconsistent use of UNRELEASED in debian/changelog. Some people do not use it at all, and it can make working on team packages harder. Indeed, if you try to modify a package, if people don't use UNRELEASED, you first need to check if the current VCS version has been uploaded to the archive or not. This complicates the life of people doing mass updates, as they can't rely on packages with `unstable` having been uploaded. This be can seen for example in the latest batch of updates by onovy, where new versions of a package were made instead of marking changes as addition to a yet to be released version, because some packages were marked `unstable` but hadn't been uploaded. I don't think it's a lot to ask and will surely make team contributions more pleasant :) Cheers, [1]: https://salsa.debian.org/python-team/tools/python-modules/-/merge_requests/15 -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc Description: OpenPGP digital signature
Re: Policy proposal: Consistent use of UNRELEASED in debian/changelog
Hi, El dom., 27 de sep. de 2020 a la(s) 21:08, Louis-Philippe Véronneau ( po...@debian.org) escribió: > Hi! > > I am proposing a minor addition to the DPT policy to try to make the use > of UNRELEASED in debian/changelog more consistent. The full diff can be > found here [1]. > > The problem this tries to solves is inconsistent use of UNRELEASED in > debian/changelog. Some people do not use it at all, and it can make > working on team packages harder. > > Indeed, if you try to modify a package, if people don't use UNRELEASED, > you first need to check if the current VCS version has been uploaded to > the archive or not. This complicates the life of people doing mass > updates, as they can't rely on packages with `unstable` having been > uploaded. > > This be can seen for example in the latest batch of updates by onovy, > where new versions of a package were made instead of marking changes as > addition to a yet to be released version, because some packages were > marked `unstable` but hadn't been uploaded. > > I don't think it's a lot to ask and will surely make team contributions > more pleasant :) > > Yes, +1 for this please. Cheers, eamanu Cheers, > > [1]: > > https://salsa.debian.org/python-team/tools/python-modules/-/merge_requests/15 > > -- > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau > ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org > ⠈⠳⣄ > >
Re: Policy proposal: Consistent use of UNRELEASED in debian/changelog
On Mon, 28 Sep 2020 at 01:08, Louis-Philippe Véronneau wrote: > > Hi! > > I am proposing a minor addition to the DPT policy to try to make the use > of UNRELEASED in debian/changelog more consistent. The full diff can be > found here +1. Seems to match what we do in the Perl team. Thanks, Nick
