When you expect that an area will get a lot of attention so that you need to do some project planning around it, it's nice to have a tracker bug. This bug is put in the "Bug ABCXYZ blocks" field. This allows you to create a dependency tree.
This is the tracker bug for feature requests and bugs against the FDP toolchain:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=fdp-toolchain-traqr
If you like numbers, because you'll need to use them too:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=156150
- Karsten
On Wed, 2005-04-27 at 14:14 -0700, Karsten Wade wrote:
When you expect that an area will get a lot of attention so that you need to do some project planning around it, it's nice to have a tracker bug. This bug is put in the "Bug ABCXYZ blocks" field. This allows you to create a dependency tree.
This is the tracker bug for feature requests and bugs against the FDP toolchain:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=fdp-toolchain-traqr
If you like numbers, because you'll need to use them too:
Karsten, could you edit this bug,
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131160
which is the Documentation Guide work tracker bug, to give it an id tag? Thanks!
On Wed, 2005-04-27 at 19:42 -0400, Paul W. Frields wrote:
Karsten, could you edit this bug,
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=131160
which is the Documentation Guide work tracker bug, to give it an id tag? Thanks!
Like this?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=fdp-docguide-traqr
Sure thing.
- Karsten
docs@lists.stg.fedoraproject.org