Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1218853

Summary:	Typo in Fedora 22 KDE Beta release notes
Product:	[Retired] Fedora Documentation	Reporter:	Penelope Fudd <bugzilla.redhat.com>
Component:	release-notes	Assignee:	Release Notes Tracker <relnotes>
Status:	CLOSED EOL	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	relnotes, wb8rcr, zach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-07 15:29:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Penelope Fudd 2015-05-06 04:07:21 UTC

Description of problem:
The release notes on the Fedora 22 KDE Beta refers to itself as Fedora 19.

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

How reproducible:
Always

Steps to Reproduce:
1. file:///usr/share/doc/fedora-release-notes/en-US/sect-Release_Notes-Welcome_to_Fedora_22.html#sect-Release_Notes-Welcome_to_Fedora
2. Look at section 1.3.2
3. See "Graphical installation of Fedora 19 requires"...

Actual results:
It says Fedora 19

Expected results:
It should say Fedora 22

Additional info:

Comment 1 Penelope Fudd 2015-05-06 04:13:48 UTC

Also, many of the links on that page take you to Fedora 19 materials:

Section 1.2: The link that says "Fedora 22 Features" goes to http://fedoraproject.org/wiki/Releases/19/FeatureList

The link that says "http://fedoraproject.org/wiki/Releases/22/FeatureList" actually goes to http://fedoraproject.org/wiki/Releases/19/FeatureList

Section 1.4.1: The link that says "Common F22 bugs" goes to http://fedoraproject.org/wiki/Common_F19_bugs

Comment 2 Petr Bokoc 2019-11-07 15:29:53 UTC

I'm closing this bug as part of a Bugzilla cleanup effort. The most likely reason is that the bug has been opened either against a component we no longer publish, or against Release Notes for an EOL release.