Update CHANGELOG and RELEASE_NOTES with tango-controls#541 and tango-…

…controls#542

CHANGELOG.md

@@ -41,6 +41,7 @@ The patch provided in [#520][pr-520] ignores such failure.
 - Fix appveyor.yml after appveyor windows image update ([#537][pr-537])
 - Fix event compatibility issues with device servers exporting Device_4 devices. Fix bug with Pipe, Data Ready and 
 Device Interface Change events. Fix event channel name issues in these different cases. ([#492][i-492], [#531][pr-531])
+- Fix WAttribute::rollback() for DevUshort WRITE attributes ([#541][i-541], [#542][pr-542])
 
 ## [9.3.2] - 2018-09-12 [unstable]
 ### Added
@@ -278,4 +279,6 @@ where a client application might show out of date/incorrect values.
 [pr-531]: https://github.com/tango-controls/cppTango/pull/531
 [pr-533]: https://github.com/tango-controls/cppTango/pull/533
 [pr-537]: https://github.com/tango-controls/cppTango/pull/537
-[pr-539]: https://github.com/tango-controls/cppTango/pull/539
+[pr-539]: https://github.com/tango-controls/cppTango/pull/539
+[i-541]: https://github.com/tango-controls/cppTango/issues/541
+[pr-542]: https://github.com/tango-controls/cppTango/pull/542

RELEASE_NOTES.md

@@ -187,6 +187,12 @@ phase (write hardware at init feature).
 If you didn't understand anything to this explanation, you were probably not affected by this bug.
 * We fixed a memory leak in get_device_property() which was occurring only on Windows and only when using Visual Studio 
 10 compiler or an older MSVC compiler version.
+* If you are not using DevUShort WRITE only attributes, you can skip to the next item.
+Still reading? So you are really using DevUShort WRITE only attributes?
+The DevUShort WRITE attribute value was not rolled back correctly to the previous valid value in some specific cases 
+(exception thrown in the device server write method associated to this attribute, exception thrown by 
+read_attr_hardware() method or exception thrown because it is not allowed to read this attribute in the current state).
+Now it is!
 * We fixed many compilation warnings and build errors with recent compilers and with Doxygen
 
 ## Changelog