Nut upsuser - Dec 2024 - How about a little game of... Re: lease?

Hello all,

  As the holiday season looms upon us, and NUT cracker sounds can be heard
everywhere, I wonder if the current codebase is good enough to cut a 2.8.3
release some time soonish.

  Active development of recently contributed drivers has somewhat subsided;
there are still some planned revisions (notably about documentation and
statuses for ECO and similar modes), but some more get shelved as potential
risk to be merged after a release.

  So as you might get a few free days for tinkering - please take a look at
building and running the current git master branch builds. The NEWS.adoc
and UPGRADING.adoc should do a good job about highlighting the changes that
have landed.

  If I were to name one subject of interest, I'd say CPS HID that got
revised broken USB report descriptor fix-up code, so hopefully fixes some
problems with voltage reporting and does not regress where it previously
worked.

  One more interesting subject regards UPS shutdowns - now the `sdcommands`
option should be handled by all drivers so deployments can specify an
INSTCMD that is more correct for their model (or even run-time situation)
than the hard-coded one. Perhaps you might test shutdowns by just toggling
the beeper or calibration - without inducing a power outage, who knows?..

  For the hackers out there, it would be nice to reproduce and nail a
problem with APC Modbus with libusb: it segfaults for some users, see issue
2289 for details :\

Hoping for feedback,
Jim Klimov
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsdev/attachments/20241219/d6f07ef1/attachment.htm>

Jim Klimov via Nut-upsdev <nut-upsdev at alioth-lists.debian.net> writes:
>   As the holiday season looms upon us, and NUT cracker sounds can be heard
> everywhere, I wonder if the current codebase is good enough to cut a 2.8.3
> release some time soonish.
My standard opinion is that this is usually true, and the path forward
is to declare it probably good enough, hold off on non-bugfix changes,
tset from this list, and then hoist a beta or rc for more testing, and
fix problems.  The other approach is to just not release and that
doesn't result in a good release either!
>   So as you might get a few free days for tinkering - please take a look at
> building and running the current git master branch builds. The NEWS.adoc
> and UPGRADING.adoc should do a good job about highlighting the changes that
> have landed.
Will do, and I'll update the pkgsrc-wip snapshot package and test it
live.