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

Bug 1401342

Summary:	Link of "Common F25 Bugs" is wrong
Product:	[Retired] Fedora Documentation	Reporter:	Edgar Hoch <edgar.hoch>
Component:	release-notes	Assignee:	Pete Travis <me>
Status:	CLOSED EOL	QA Contact:	Fedora Docs QA <docs-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	devel	CC:	me, pbokoc, relnotes, wb8rcr, zach
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-07 15:30:06 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 Edgar Hoch 2016-12-04 23:27:16 UTC

Description of problem:
In section 1.4.1. of Fedora 25 Release Notes the link of "Common F25 Bugs" is wrong:

The link is
http://fedoraproject.org/wiki/Common_25_bugs
but it should be
http://fedoraproject.org/wiki/Common_F25_bugs

Version-Release number of selected component (if applicable):
https://docs.fedoraproject.org/en-US/Fedora/25/html/Release_Notes/sect-Release_Notes-Welcome_to_Fedora_.html

Please fix it in the online documentation asap because many users will run into "New page" in Fedora Wiki instead of the list of common bugs! It is not enough to update it in somewhere in the devel version (as done in the past with other release note link errors which I have reported).

Comment 1 Petr Bokoc 2016-12-05 12:39:34 UTC

Hello Edgar, thanks for the report. I fixed the link on the F25 release branch and on master, so the change should carry forward into subsequent releases. I can't republish books very easily, however, so I'll ask Pete Travis to publish the updated version later today.

Comment 2 Petr Bokoc 2019-11-07 15:30:06 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.