<div dir="auto"><div>Thank you for the test and report!<div dir="auto"><br></div><div dir="auto"> Regarding the changes, I hoped the NEWS and UPGRADING files detail them extensively enough :)</div><div dir="auto"><br></div><div dir="auto"> Protocol-wise, there were some aliases added, and one notable change was addition of TRACKING for queries and replies to not mix up, more so with massive setups of many devices. Servers and clients of different versions should be compatible both ways though; tested vs 2.7.4 during development.</div><div dir="auto"><br></div><div dir="auto">Jim</div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 1, 2022, 15:40 René Garcia via Nut-upsdev <<a href="mailto:nut-upsdev@alioth-lists.debian.net">nut-upsdev@alioth-lists.debian.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I built successfully package with 2.8.0-rc1 for VMware ESXi (6.7 and 7.0 tested). Now, this package provides only the client part of NUT (upsc and upsmon) and I think that this part of code has few evolutions since 2.7.4<br>
<br>
Client has to be able to communicate with NUT servers running older versions as customers may not be able to chose server version. I did not notice significant network protocol changes in 2.8.0 (no change at all ?) and every test I did has ran fine.<br>
<br>
Thank you,<br>
René<br>
<br>
<br>
> Le 1 avr. 2022 à 02:01, Jim Klimov via Nut-upsdev <<a href="mailto:nut-upsdev@alioth-lists.debian.net" target="_blank" rel="noreferrer">nut-upsdev@alioth-lists.debian.net</a>> a écrit :<br>
> <br>
> Hello, fellow NUTs!<br>
> <br>
> It is with a [happy] heart that I must proclaim today, that the long reign of NUT v2.7.4 is coming to an end. Its anticipated successor of half a dozen years, release-in-waiting NUT v2.7.5 has also quietly expired, and [won't] be sorely missed. They were survived by the next name in line, NUT v2.8.0(-rc1). Le NUT est mort, long live the NUT!<br>
> <br>
> Along just this leg of the journey, NUT codebase survived at least four separate CI farms and technologies to make its builds easier and more reliable, all while succeeding on a wide range of CPU and OS platforms, ranging from current distros to the dawn of millenium (nearly-immutable appliances and sturdy reliable servers matter too!), as well as multiple generations and implementations of compiler toolkits, "make" and scripted code interpreters involved.<br>
> <br>
> We are grateful to the many freely available projects, services and communities who helped us in particular (maybe unwittingly) and the FOSS ecosystem in general (intentionally), such as (and not limited to) Asciidoc, Autotools and family, BuildBot, CCache, Clang/LLVM, FossHost, GCC, GitHub, Google, illumos, Jenkins, LiberaChat, Proxmox, QEMU, StackExchange, Travis, ZeroMQ... bits here, swathes there - it would have been much harder without the likes of them (and many others).<br>
> <br>
> Advances in compiler code analysis in particular, as is seen on a daily basis with CI non-regression builds across the range of 10 major releases of clang and 7 of gcc, is immense. At times annoying, yes, but it led to a great cleansing of the codebase from questionable code (and indeed some potential bugs). And it was possible to do so in a way that all those regularly tested systems are satisfied, so the codebase stays clean and green and portable as we iterate new contributions, and merged with peace of mind many ports and features from long-awaited branches (such as libusb-1.0+0.1 support finally), or forks (notably 42ity/nut).<br>
> <br>
> Let me take a moment to tender our special thanks from both the maintainer team and countless users of UPS, ePDU, solar panel and similar hardware, to numerous personal and corporate contributors of new drivers and features or fixes for existing ones, as well as to community members who ask and answer questions, and who log github issues with their ideas, experiences or grievances.<br>
> <br>
> As always we would welcome people willing to regularly share their expertise in certain areas and tools (in particular, thanks @nbriggs for solving many practical mysteries around USB bit-stream lately), or protocols (more active experts on prolific Qx family would be great for PR reviews), or packaging, service and distro integrations, or HCL/DDL maintenance based on reports trickling in... just about anything!<br>
> <br>
> While we have a lot of features queued to complete or port for the next releases (hopefully with a healthier cadence), we expect to see more feedback by exposing thevrelease, and hope for little fallout from the many changes made while cleaning up the warnings.<br>
> <br>
> Handing over to creative packagers now...<br>
> <br>
> Jim Klimov,<br>
> on behalf of the Network UPS Tools Project<br>
> _______________________________________________<br>
> Nut-upsdev mailing list<br>
> <a href="mailto:Nut-upsdev@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsdev@alioth-lists.debian.net</a><br>
> <a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a><br>
<br>
<br>
_______________________________________________<br>
Nut-upsdev mailing list<br>
<a href="mailto:Nut-upsdev@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsdev@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev</a><br>
</blockquote></div></div></div>