Hi Santiago,
On 18/6/23 03:04, Gioele Barabucci wrote:
One can use the mechanism discussed in section 5.14.3 of the Developer's
Reference [1]:
1) Block the automatic migration via britney/excuses.
2) When a new version is released, dput two different versions: one into
unstable and one into testing-proposed-updates.
To reduce the amount of work needed for each update of `base-files`,
`/etc/os-release` can be moved to package like `debian-version-info`, so
the manual double upload must be done only once per release cycle.
[1]
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#direct-updates-to-testing
What are your thoughts on this proposal?
Thanks,
Harshula