On wiki page http://www.ovirt.org/Quick_Start_Guide (derived from https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.0/html/Quick_Start_Guide/index.html) there are a number of dead links - "oVirt Node deployment documentation", "oVirt Installation Guide", "oVirt Node Deployment Guide" (and perhaps others). As one of the first pages new users find when searching for documentation on installation, we should ensure that the instructions are well maintained, with no dead links.
This component was created for tracking issues with the PDF Installation Guide which was ultimately only produced for oVirt 3.0. By virtue of being a wiki the Quick Start is editable by all and thus no Bugzilla component was ever required/created.
Hi Steve, Would you mind maintaining the component, and making it for the "getting started docs" in the wiki? I don't mind if we change the detfault assignee, but would like to maintain this as a bug - this is the only bug tracker we've got. Thanks, Dave.
(In reply to Dave Neary from comment #2) > Hi Steve, > > Would you mind maintaining the component, and making it for the "getting > started docs" in the wiki? I don't mind if we change the detfault assignee, > but would like to maintain this as a bug - this is the only bug tracker > we've got. > > Thanks, > Dave. No, if you need/want a new component then request one via the normal process - all bugs under this component have just been cleared up and it only exists for historical reasons.
This is an automated message. Re-targeting all non-blocker bugs still open on 3.4.0 to 3.4.1.
This is an automated message. oVirt 3.4.1 has been released. This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.
Okay, I have gone through and ensured that all the links are indeed live. I still want to update the Quick Start Guide to 3.5. Do we close this bug and open a new one?
Moving pending bugs not fixed in 3.5.0 to 3.5.1.
oVirt 3.5.1 has been released, re-targeting to 3.5.2 as marked as urgent / high priority
Re-targeting to 3.5.3 since this bug has not been marked as blocker for 3.5.2 and we have already released 3.5.2 Release Candidate.
Brian is this bug still valid?