On Sun, 2005-08-21 at 17:50 -0400, Paul W. Frields wrote: > Now that we have our own product and components for docs, it seems to me > that the "per-document" trackers, such as: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=ig-traqr > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=fdp-docguide-traqr > > ...have been rendered obsolete. I still like the idea of keeping the > tracker bugs for ideas and works-in-progress, although I suspect they > will be ignored in favor of the Wiki. (*sigh*) Comments? Grayland. Landscape unclear. I think tracker bugs came about as a way of showing a dependency relationship outside of the individual components. So, they work best for situations such as "blocker for FC5" or "docs ready for publishing". Those are keepers. There are other reasons to have a tracker that is for a single document. For example, you may want to have code related bugs be blocking, so that the resolution of those bug reports is tracked. In this second case, it's up to the author/editor if they need it. Seeing as how that describes you for both those bugs, I think you know best if they are needed. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list@xxxxxxxxxx To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-docs-list
