Bug 168083 (fc5-relnotes-traqr)

Summary:	FC5 release notes tracker bug
Product:	[Fedora] Fedora	Reporter:	Gavin Henry <ghenry>
Component:	fedora-docs	Assignee:	Release Notes Tracker <relnotes>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Tammy Fox <tammy.c.fox>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	ghenry, kwade
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Process
Whiteboard:
Fixed In Version:	FC5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-02 17:18:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	166916, 172822, 173777, 175787, 176186, 176749, 177753, 177754, 177756, 177757, 177758, 178573, 178847, 178965, 179584, 179794, 179798, 179799, 181689, 181808, 182551, 182639, 182677, 182705, 184455, 680165, 1060216, 1158767
Bug Blocks:	151189

Description Gavin Henry 2005-09-12 09:52:31 UTC

Description of problem, bug, incorrect information, or enhancement request:

Opening first bug report for FC5 relnotes.

Version of release notes this bug refers to:

Fedora Core 5 final release

Comment 1 Karsten Wade 2005-09-12 21:35:52 UTC

Cool, this bug should block all relnote beat reports that come in for FC5.  Thanks.

Comment 2 Karsten Wade 2005-09-15 18:54:57 UTC

I just looked, and bug #151189 has been considered canonical for tracking all
bug reports.  I'm going to add this bug as a blocker to that one, just to keep
track of where this one goes.

Is it valuable to have a separate sub-master tracker for each release?  We shall
see.

Comment 3 Karsten Wade 2006-07-02 17:18:21 UTC

We have had no reports of bugs in the release notes for FC5 and we are now
approacing FC6 test2.  Therefore, we're closing this tracking bug as we do not
anticipate taking or fixing any relnotes bugs for FC5.

If a new bug is opened and found to be valid, it can be set to block this bug
without having to reopen this bug; that would be helpful for historical
tracking, at least.