MySQL Bugs: #42706: Determining MEM version updates and changes from documentation

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

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.

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.

Patch installed in versions => 2.1.0.1039.

verified the readme now references Appendix D

No documentation needed.