[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: reopening bugs closed by removal after package reintroduction?



Hi,

Il 05/05/20 09:14, Paul Wise ha scritto:
> Should we also be triaging the bugs filed against removed versioned
> source packages like golang-1.9 or python3.6?

For Boost packages I manually reassign bugs that are still relevant to
the newer Boost version whenever one old version gets removed from the
archive. Fortunately Boost tend to have a relatively manageable number
of bugs, so that this does not require a terrible amount of work. Also,
it has the nice side effect to force me to retriage them periodically,
prune those that do not apply any more and remind me of the others.

(context for those who are not aware of it: the Boost library is
uploaded as a NEW versioned source package at each major release that
ends up in Debian, which the source package boost-defaults providing
versionless pure-dependency packages to the current default version)

In the specific case of Boost, I don't feel the need for an automated
procedure, because the bugs are not that many, and there is not clear
majority between bugs that need to be reassigned and those which do not.
So the amount of manual retriaging work is more or less the same. On the
other hand, I know I am doing that work anyway. Maybe at a project level
it is better to not assume that the maintainer won't be lazy, and keep
the bugs by default, giving of course the maintainer (as always) the
option to dismiss bugs that do not apply any more.

HTH, Giovanni.
-- 
Giovanni Mascellani <g.mascellani@gmail.com>
Postdoc researcher - Université Libre de Bruxelles

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: