[publican-list] [Bug 695545] RFE: make doc root configurable

bugzilla at redhat.com bugzilla at redhat.com
Tue May 8 22:58:04 UTC 2012


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=695545

--- Comment #10 from Jared MORGAN <jmorgan at redhat.com> 2012-05-08 18:58:02 EDT ---
(In reply to comment #9)
> (In reply to comment #8)
> > I've also observed that the parameters mentioned are not present in any staged
> > version of the Publican User Guide. These probably need to be documented as
> > part of this issue, before being marked as VERIFIED?
> 
> Oh we don't have a process for updating the PUG from RFE's ... How about we
> make one?
> 
> My suggestion:
> 
> 1: Create a BZ for updating the PUG for version X.Y.
> 2: When an RFE bug gets verified we change the status to verified and link the
> RFE bug to the PUG update bug.
> 3: We assign the PUG update bug to Rudi :D
> 
> Step 2 could be a 'See Also' or a 'Blocks', as long as the person doing the PUG
> update knows they need to document something.

I think your suggestion works well, Jeff.

Have an umbrella ticket for all PUG 3.0 issues derived from RFE, or other
enhancements that add parameters or undocumented functionality. I like the idea
of linking other BZ issues into the main ticket as the primary tracker. 

I think Blocks would be the correct status to set for linked bugs: the status
of the bug would be reflected with strikethrough once it was completed (or
ready to document). 

If the person documenting the issue has any questions, they ask the questions
in the linked development RFE to keep the info together (rather than in the PUG
3.0 umbrella ticket).

I'll get the ball rolling on this.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.




More information about the publican-list mailing list