On Sun, Sep 20, 2020 at 12:31:13AM +0100, Sudip Mukherjee wrote: > HI Mattia, > > On Sat, Sep 19, 2020 at 8:58 PM Mattia Rizzolo <mattia@debian.org> wrote: > > > > On Sat, Sep 19, 2020 at 08:39:44PM +0100, Sudip Mukherjee wrote: > > > After discussing with few people, I now intend to file them with > > > "severity: important" and I will also reduce the severity of the > > > previously open similar bugs to 'important'. > > > > That's good. > > > > But please also share your proposed text with this list (as the MBF > > rules asks for). Your past filings where IMHO written with a tone that > > could be improved. Also I would like to make sure that you include > > stuff like your plans with the severity, references to the release team > > decisions, etc. > > Apologies for the tone. It was my first MBF and I was struggling to > make the text more generalised so that it will work for all the > packages in the list. > For this new list of packages, how is the following text: > > ********************************************************************************************** > > Subject: <package>: autopkgtest must be marked superficial > severity: important > > Dear maintainer, > > It has been noticed that the autpkgtest in <package> is running a > trivial command. > - <list the command being run> > > Those kind of tests are considered to not provide significant coverage > for a package as a whole, and as such the keyword "Restrictions: > superficial" has been defined [1]. Packages with all tests marked as > 'superficial' are not considered for the reduced migration age from > unstable to testing and also they will not be allowed to migrate in a > later stage of the freeze [2]. > > The Release Team has listed this issue in the list of Release Critical > Issues for bullseye [3] and has mentioned that the test must be marked > superficial if it is not testing one of its own installed binary > packages in some way. > > > [1]. https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst > [2]. https://release.debian.org/bullseye/freeze_policy.html > [3]. https://release.debian.org/bullseye/rc_policy.txt Maybe you could include something like this (the wording can be improved): Note, however, that such superficial tests are still somewhat useful, as they will be considered, for example, to block dependencies from breaking your package. In other words, please do not react to this bug report by dropping tests from your package completely. More extensive testing is of course better, but even superficial tests are better for the overal quality of Debian than no tests at all. We want to avoid maintainers panicking and just dropping the tests as a response do this MBF.
Attachment:
signature.asc
Description: PGP signature