Bug 479979 - Installation Doc - Draft Stamp in GR Version
Installation Doc - Draft Stamp in GR Version
Status: CLOSED WONTFIX
Product: Fedora Documentation
Classification: Fedora
Component: install-guide (Show other bugs)
devel
All Linux
low Severity medium
: ---
: ---
Assigned To: David Nalley
Paul W. Frields
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-14 07:12 EST by Dustin
Modified: 2009-06-18 00:56 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-18 00:56:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot of Stamp Page (105.86 KB, image/jpeg)
2009-01-14 07:12 EST, Dustin
no flags Details

  None (edit)
Description Dustin 2009-01-14 07:12:37 EST
Created attachment 328976 [details]
Screenshot of Stamp Page

Description of problem:

I just downloaded the Fedora10 Install doc from http://docs.fedoraproject.org/install-guide/f10/en_US.  However, when I opened the document, it displayed a large 'DRAFT' Not for Reference Stamp on it. I have a screenshot if you would like, but for fear that your mail may block unsolicited image attachments I just wanted to describe the problem, and if you would like the screenshot let me know and I will provide it.
Version-Release number of selected component (if applicable):


How reproducible:
I just downloaded the Fedora10 Install doc from http://docs.fedoraproject.org/install-guide/f10/en_US.  However, when I opened the document, it displayed a large 'DRAFT' Not for Reference Stamp on it.

Steps to Reproduce:
1. Go to URL: http://docs.fedoraproject.org/install-guide/f10/en_US
2. Download the Document, and Open it
3. View the red 'DRAFT' Not for Refrence Stamp
  
Actual results:


Expected results:
This Draft should have been removed in the GR version of this doc.

Additional info:
Comment 1 Karsten Wade 2009-01-14 12:25:05 EST
I think this probably happens in *all* of the HTML tarballs of the Installation Guide.  When building the HTML, we need to set a flag to not be DRAFT and I'm sure we didn't. :)

Two options come to mind:

1. Rebuild as-is and repost

2. Finish converting the guide to Publican, then use Publican to repost (including a new PDF version)

Jared Smith was going to look more in to the IG conversion, while taking notes; I sent him that on the last day of FUDCon.  If he's made enough progress, we might want to proceed with the second option.
Comment 2 Dustin 2009-01-14 21:00:29 EST
I would like to offer my assistance in moving forward with converting the guide to publican.  I realize this is my introduction into the documentation community, but I have a great interest in taking up this project to start giving back to the community for this project, as well as perhaps help take efforts off of other otherwise "overloaded" plates.  If you have a list of tasks left to complete the conversion, and the latest source for the guide I work towards this end result.

(In reply to comment #1)
> I think this probably happens in *all* of the HTML tarballs of the Installation
> Guide.  When building the HTML, we need to set a flag to not be DRAFT and I'm
> sure we didn't. :)
> 
> Two options come to mind:
> 
> 1. Rebuild as-is and repost
> 
> 2. Finish converting the guide to Publican, then use Publican to repost
> (including a new PDF version)
> 
> Jared Smith was going to look more in to the IG conversion, while taking notes;
> I sent him that on the last day of FUDCon.  If he's made enough progress, we
> might want to proceed with the second option.
Comment 3 Ruediger Landmann 2009-06-18 00:56:06 EDT
With the release of F11 and the move of the Installation Guide to Publican, there probably isn't any real need to fix this.

If someone has the necessary skills with the old docs tools and would like to rebuild the F10 book with them, please re-open the bug.

Note You need to log in before you can comment on or make changes to this bug.