By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 1813

Summary:	[Help Handbooks] Add a bugzilla option to ensure help handbooks are reviewed
Product:	TDE	Reporter:	Darrell <darrella>
Component:	other (any)	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	bugwatch, darrella, kb9vqf, michele.calgaro, midenok, wofgdkncxojef
Priority:	P1
Version:	R14.0.x [Trinity]
Hardware:	Other
OS:	Linux
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Bug Depends on:
Bug Blocks:	2914

Description Darrell 2014-01-07 18:46:43 CST

Documentation is always a challenge in a software project. We need a mechanism in the bugzilla to ensure that whoever closes the bug report has verified, or has verified with an appropriate documentation maintainer, that any related help handbooks have been reviewed for related updates and revisions.

Without such a mechanism the status of the handbooks will continually deteriorate.

Comment 1 Timothy Pearson 2014-01-07 22:24:50 CST

How would this most efficiently be implemented?  I added a status for FIXED_INDOCREVIEW, but have no way of forcing users to set that status before they set FIXED.

Comment 2 Darrell 2014-01-08 00:42:12 CST

Perhaps somebody searches for bug reports closed as FIXED (rather than FIXED_INDOCREVIEW). When any report is closed as FIXED, somebody reviews the report for relevance to handbook updates. When the reviewer decides nothing was related to handbook updates then the reviewer updates the report as RESOLVED FIXED_INDOCREVIEW. When the reviewer decides handbook updates are needed then reopen the bug report and add a related comment.

When we reopen a bug report, to draw attention to handbook updates, then perhaps we have a Status option of DOCREVIEW (like PATCHAVAIL). When the handbook is finally updated then the report is closed as RESOLVED FIXED_INDOCREVIEW.

When a bug is resolved technically but a reviewer decides there are handbook updates associated, the report is not closed as RESOLVED FIXED but tagged as DOCREVIEW. Whoever is involved with handbook maintenace, such as myself, then can search for such reports more readily. 

Not smooth but a start.

If we pass the word on the dev mail list we all can start watching for this.

Is there a way to restrict closing bug reports only to certain people on the development team? Perhaps then we have some kind of damage control?

Comment 3 Darrell 2014-01-15 20:03:58 CST

Tim,

If you add a Status option of DOCREVIEW then we can close this report. The review process will remain manual but at least we would have a tracking process.

Comment 4 Michele Calgaro 2014-03-07 01:38:59 CST

Tim, can you add the DOCREVIEW status? By the way, where has the CONFIRMED status gone?

Comment 5 Aleksey Midenkov 2014-05-20 03:02:13 CDT

Why it's critical? It doesn't prevent any software usability. Should be 'major'.

Comment 6 Michele Calgaro 2014-05-20 04:45:35 CDT

Downgraded to 'normal': Aleksey's comment is spot on.

Tim, can you add the DOCREVIEW status (between PATCHAVAIL and RESOLVED would be nice) so that we can close this bug?

Comment 7 Michele Calgaro 2018-08-01 05:09:40 CDT

There is no one that would be doing the doc review, and the original reporter is no longer active in TDE (unfortunately ;-( Darrell was a very good tester...)