Bug 230509 - Inconsistent reference to RHEL 4.5 versus RHEL 4 update 5
Inconsistent reference to RHEL 4.5 versus RHEL 4 update 5
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: Documentation (Show other bugs)
4.5
All Linux
medium Severity medium
: ---
: ---
Assigned To: Don Domingo
John Ha
http://www.redhat.com/docs/manuals/en...
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-28 22:48 EST by Riaan van Niekerk
Modified: 2014-08-04 18:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-01-20 21:19:25 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 Riaan van Niekerk 2007-02-28 22:48:51 EST
Many pages on the RH web site use the new naming convention, e.g. 4.5 in
http://www.redhat.com/docs/
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/index.html

Many pages still use the old naming convention, e.g. 4 Update 5:

http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/release-notes/
RELEASE-NOTES-U5-x86-en.html
https://rhn.redhat.com/network/software/channels/downloads.pxt?cid=2570

Will these terms be interchangeable for the short to medium term, or should the 
new convention be followed consistently throughout? (the former is causing some 
confusion with my customers)
Comment 2 Michael Hideo 2007-10-22 22:45:05 EDT
Removing automation notification
Comment 3 Don Domingo 2008-01-20 21:19:25 EST
moving forward, the correct naming convention should be purely numeral, e.g. Red
Hat Enterprise Linux 4.5.0.

all post-RHEL5 documentation use this now. if there are any outstanding
documentation (except for release notes) that still use the incorrect convention
(RHEL 4 Update 5) they should be reported as bugs.

closing this bug out. sorry for the delay.

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