Hi, Ludovic Courtès <[email protected]> writes:
[...] > I’ve been thinking about it, and it seems there’s already quite a bit in > the manual, as Giovanni noted. We could add a note about libabigail’s > ‘abidiff’ under “Security Updates”, and one about ‘package/inherit’. Thanks, abidiff is the tool I was thinking about. There's already information there, but it wouldn't hurt to at least document package/inherit. The abidiff flow could go in the cookbook. > Because that’s a lot of information, an idea that came to mind is that > the security team could review changes that introduce a ‘replacement’ > field for ABI issues and other issues. It seems like an easy change > that would catch things like attempting to rename a .so file. > > Thought? That's also a good idea, but I don't think this can be automated using the current CODEOWNERS logic, which can only group which files are in a given scope, so we'd have to rely on humans to not forget tagging the security team. -- Thanks, Maxim
