About that documentation refresh... as the new news entry on nut-website goes:
Are you wondering how NUT Quality Assurance and Build Automation <https://networkupstools.org/docs/qa-guide.chunked/index.html> happens? Perhaps you want to do similar feats in your project? Well, now I can say "I wrote a book on that!" :) A few chapters were moved from Developer Guide and User Manual into a new NUT QA&BA Guide, more existing README's in various subdirectories were included as chapters about those tools, and new ones were written to detail the NUT CI farm and lessons learned from moving its core from Fosshost to DigitalOcean's sponsored VMs. You can now see automated renders of the document at the nut-website: - https://networkupstools.org/docs/qa-guide.pdf - https://networkupstools.org/docs/qa-guide.chunked/index.html If you run a project that might benefit from our experience, or seeks ideas what else/how else to test it, and especially if like NUT it is a massively multiplatform endeavour where you need to juggle significantly different generations of OSes/toolkits/languages -- feel free to be inspired :) Hope this helps, Jim Klimov On Fri, Mar 28, 2025, 10:27 Jim Klimov <[email protected]> wrote: > Hello all, > > It has been too long that I was feeling a release is just around the > corner, just gotta tie up a few loose ends. The significant ones we had are > finally tied, some others delayed to v2.8.4 trail, and a documentation > refresh remains. Thanks to some package maintainers taking a look at the > master branch, some issues with "dist" archive creation and parallel builds > were also located and addressed. > > So, it is that time of the year again, folks, when flowers bloom and > code gets ripe for picking a new release snapshot -- so everybody is > welcome to give it a round during the weekend. After too many hopeful > deadlines missed, I hope to at least not exceed a year since the last > release snapshot :) > > As usual, > https://github.com/networkupstools/nut/wiki/Building-NUT-for-in%E2%80%90place-upgrades-or-non%E2%80%90disruptive-tests > (and the build prerequisites linked from there as > https://networkupstools.org/docs/user-manual.chunked/_build_prerequisites_to_make_nut_from_scratch_on_various_operating_systems.html) > should help you get started. > > Hoping for good news and no blocker issues, > Jim Klimov > > PS: One known problem remains with the recently introduced apc_modbus > driver and/or the libmodbus (core or our fork with rtu_usb branch) - that > the USB connections tend to fall apart, as tracked at > https://github.com/networkupstools/nut/issues/2609 and others linked from > it - for now I've exhausted the hardware-less ideas and the time I had; > help is welcome. >
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
