On Mon, Jun 15, 2009 at 6:16 AM, Berend-Jan Wever<[email protected]> wrote: > Before we start creating a list, we should think of a procedure that will > make sure it is kept up-to-date. It makes no sense if we create the list now > only to find that a year from now, when we need it, it's outdated. > The two most important questions to me at this point are: > - Were should we keep this information? > - How do we keep this information up-to-date when code changes?
That's very tough to do. The "shared document" approach generally falls apart pretty quickly. One could imagine using a "SECURITY=" line in commit messages like the "TEST=" line. But someone would need to run `git log` every so often and check them out. I'm not sure that there is a good solution to this. AGL --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
