Hello Vej, indeed, it's a kind of a "special triaging rule for this package" (in this case), since this bug came from a customer, and therefore a 'Package to team mapping' applies (that's agreed uppon with the teams - in this case Foundations). In this particular case I remembered the latest updates of that package, double checked the changelog again, and had a quick chat with the maintainer - so the maintainer and team were well aware.
But good point - I assumed such a question - since I'm doing this (in my job) now and then - but _always_ in agreement with the particular teams. BR, Frank On Sun, Nov 10, 2019 at 3:18 PM Vej <ubu...@jonasdiekmann.de> wrote: > Hello Frank, > > I have one question regarding your application: > > You say that you assigned bug 1814521 to a team. Is that because of a > special triaging rule for this package or an applicable rule for this team? > > Because otherwise it is not a good practice to assign bugs to people or > teams without there knowledge, as an assigned bug might not be touched by > other developers as they might believe it to be worked on by the assigned > team. > > Best regards > > Vej >
_______________________________________________ Mailing list: https://launchpad.net/~ubuntu-bugcontrol Post to : ubuntu-bugcontrol@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol More help : https://help.launchpad.net/ListHelp
