Finding better solutions for noting problems with packages in devel-proposed

[Simon Quigley]

Hello,

As someone who occasionally goes through the backlog on
update_excuses.html to try and find packages which could potentially
migrate, I find myself revisiting some packages and wanting to note my
findings somewhere that can't be easily spotted by using the Britney
output, such as somewhat complex Node.js dependency trees. It would be
good to have the ability to note these sort of findings somewhere, such
as an Etherpad or a wiki page so someone else (or myself a month or more
down the road) doesn't have to waste the time.

Here's a bug which relates:
https://bugs.launchpad.net/britney/+bug/1683749

But at this point we're filing bugs for packages which haven't migrated,
and people could potentially forget once they have migrated.

Has something like this ever been considered? If not, does anyone object
to me setting up something under our Etherpad instance to coordinate?

Thanks.

-- 
Simon Quigley
tsimonq2 at ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20180903/12eaa12b/attachment.sig>