Bug #42706 Determining MEM version updates and changes from documentation

Submitted: 9 Feb 2009 16:55 Modified: 21 Aug 2009 8:57
Reporter: Roger David Nay Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Enterprise Monitor: Documentation Severity:S3 (Non-critical)
Version:2.0+ OS:Any
Assigned to: Andy Bang CPU Architecture:Any

[9 Feb 2009 16:55] Roger David Nay 
Description:
The merlin 2.0.3/2.0.4 readme files state that information on > version changes is located in Appendix C. This is wrong it's located > in Appendix D.

Also, it is not easy to determine whether to download and install a new version as it is difficult see the changes introduced from one version to the next from the on-line documentation. This is made more difficult because of http://bugs.mysql.com/bug.php?id=42468 and the fact that the README link on the documentation page has the above problem. A little confusing as well the "What's new in this release".

How to repeat:
Look at the latest version 2.0.4 links and docs.

Suggested fix:
Update the README_x.txt files.

Rename the "What's new in this release" to something like "What's new in V2.0" or maybe the title of the document "Fall 2008 Release (Enterprise Monitor 2.0) What's New", and then a direct link to the version changes as well nearby OR just make the changes between releases more easily accessible with a direct link.
[5 May 2009 16:26] Andy Bang 
Agent: Pushed up to revision 1249.
Service Manager: Pushed up to revision 6627.

The reference to Appendix C has been changed to Appendix D.
Bug #42468 has been fixed, so the online docs should be up to date.
I don't agree that the What's New link needs to be renamed and have not done that.
[14 May 2009 2:23] Keith Russell 
Patch installed in versions => 2.1.0.1039.
[4 Jun 2009 20:56] Bill Weber 
verified the readme now references Appendix D
[21 Aug 2009 8:57] MC Brown 
No documentation needed.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.059 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.