NEWS.adoc, UPGRADING.adoc: clarify that PR networkupstools#266 adds I…

…MMUTABLE flag propagation on socket protocol (and fix float=>double)

Signed-off-by: Jim Klimov <[email protected]>

NEWS.adoc

@@ -137,11 +137,14 @@ https://github.com/networkupstools/nut/milestone/11
    * `upsd_cleanup()` is now traced, to more easily see that the daemon is
      exiting (and/or start-up has aborted due to configuration or run-time
      issues). Warning about "world readable" files clarified. [#2417]
-   * sanity-check `NUMBER` values that they actually resolve as a `float`
+   * sanity-check `NUMBER` values that they actually resolve as a `double`
      or `long int`; report an un-flagged type as `STRING` if not (previously
      blindly defaulted to `NUMBER` always). Debug-print presence of the
      `IMMUTABLE` flag in `netget.c::get_type()`, and actually consider it
-     in the `netset.c::set_var()` method to abort early. [#266]
+     in the `netset.c::set_var()` method to abort early. Socket protocol
+     used between a driver and data server to exchange device state was
+     updated to pass `IMMUTABLE` flag, but this change should not impact
+     the NUT network protocol as published in RFC 9271. [#266]
 
  - nut-scanner:
    * the tool relies on dynamic loading of shared objects (library files)

UPGRADING.adoc

@@ -68,10 +68,13 @@ Changes from 2.8.2 to 2.8.3
 
 - The `netset.c::set_var()` was updated to consider the `IMMUTABLE` flag on
   values to reject writing into them quickly. This is currently expected
-  to only impact `override.*` values in vanilla NUT codebase. [#266]
+  to only impact `override.*` values in vanilla NUT codebase, and should
+  not impact the NUT network protocol as published in RFC 9271 (only the
+  socket protocol used between a driver and data server to exchange device
+  state). [#266]
 
 - The `netset.c::get_type()` was updated to sanity-check `NUMBER`-flagged
-  values that the strings actually resolve into `float` or `long int`
+  values that the strings actually resolve into `double` or `long int`
   values. Some codebase does not flag its values properly and warnings
   can be emitted (to be reported for upstream NUT to fix these use-cases).
   [#266]