Bug 179306 - links to FC4 test 1 in FC5 test 2 release notes
links to FC4 test 1 in FC5 test 2 release notes
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: fedora-release (Show other bugs)
5
noarch Linux
medium Severity medium
: ---
: ---
Assigned To: David Cantrell
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-01-29 22:56 EST by Jim Cornette
Modified: 2013-01-09 20:21 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-01-29 23:01:50 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jim Cornette 2006-01-29 22:56:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051215 Fedora/1.7.12-3

Description of problem:
Reviewing the release notes after installing fedora-release showed links to Fedora Core 4 Test 1.
The links should specify values for Fedora Core 5 test 2

Version-Release number of selected component (if applicable):


How reproducible:
Didn't try

Steps to Reproduce:
1. download fedora-release for version 5 test 2
2. Install fedora-release via rpm
3. Review release notes
  

Actual Results:  The page for FC5T1 for release notes was changed to FC5T2 after rpm installation and browser refresh. The second hyperlink pointed to an item for FC4T1 and the link took me to a page related to FC4T1.

Expected Results:  The references should be for FC5T2 or should not specify any release version if information is not specific to a release but specifies valuable and not release specific information.

Additional info:
Comment 1 Rahul Sundaram 2006-01-29 23:01:50 EST

We fixed that in our latest release notes in the web. 

http://fedora.redhat.com/docs/release-notes/

Test3 should include all these fixes. Thank you for your report

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