On Fri, 2006-03-10 at 18:18 +0530, Rahul Sundaram wrote: > I strongly believe it should provide references to this information but > not include them within the release notes itself. We should provide a > list of bug reports fixed with equivalent bugzilla links. We should also > summarize and present major known issues and total bug count. Our build > system should do this along with the rawhide reports. As an example, > this is pretty useful - http://weblogs.mozillazine.org/rumblingedge/ Yes, definitely. If we do not get someone in the project to do this work, I'm hoping to grab the tail of similar tools for the RHEL side of the house. A generated table with bug # that links to the report and the bug summary. I agree, this information is desired and useful to many people. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Content Services Fedora Documentation Project http://www.redhat.com/docs http://fedoraproject.org/wiki/DocsProject
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
