On Mon, 2005-08-22 at 01:32 +0200, Peter Boy wrote:
Am Sonntag, den 21.08.2005, 17:50 -0400 schrieb Paul W. Frields:
> Now that we have our own product and components for docs, it seems to me
> that the "per-document" trackers, such as:
> ...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?
I suppose, the wiki is not very suitable to track work in progress. But
perhaps their should be a system to close a bug, e.g. with the release
of a piece of document (and open a new one for corrections, and a new
one for modifications for a new release)?? (And the wiki should have a
link to the bug entries).
WRT pieces of a doc, this you can definitely do in Bugzilla. A bug can
be closed as RAWHIDE, meaning that CVS has the fix for that bug. A bug
can be opened for a new document request ("docs-request" component), and
a chapter or section could have its own bug hooked to that request bug
by blocking it. As each section is finished, that bug is closed. When
all the bugs for the request bug are closed, it's probably ready for
final editorial. Then when it's published, if it doesn't already have
one, it will get its own bugzilla component for enhancement requests,
error reports, and so forth.
I know what's in Bugzilla seems too permanent, but it also means that
people's comments can't be discarded out of hand; the discussion is part
of the permanent record in a single place that doesn't require clumsy
surfing around the list archives. This is why so much development
discussion occurs there. Just a thought...
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/