Bill> ... that's a stupid guideline. It's a good minimum requirement, or Bill> maybe a good default, but why would you want to prevent someone from Bill> explaining in more detail *why* they made a particular change?
JBeck> Because such explanations can get very long very quickly. So we just JBeck> list the bug ID and its synopsis, then anyone who wants more details JBeck> can just go read the bug report. Alan> Assuming that unlike OpenSolaris, you have a bug database that allows Alan> people to view useful amounts of information. Yes, a key requirement. Since this was available to everyone who could see the check-in comments back in the day, the "just put the bug ID and synopsis" rigor made sense. IMO the general idea of "just put a pointer with a synopsis" still makes a great deal of sense, though the pointer may have to change to one that everyone can access, or the tool database behind it may need to change to allow greater access. -- John http://blogs.sun.com/jbeck _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
