Skip to content

2.8.3

No due date 69% complete

Since 2.8.2 leans toward being a relatively urgent bug-fix and recipe improvement release for 2.8.1, longer-termed planned ideas got moved into 2.8.3 (and original plans for 2.8.3 as the further-away future moved into 2.8.4 plan)

Point release to address tickets in general, and possible 2.8.0 fallout and 2.7.5 planned remainders that were not addressed in…

Since 2.8.2 leans toward being a relatively urgent bug-fix and recipe improvement release for 2.8.1, longer-termed planned ideas got moved into 2.8.3 (and original plans for 2.8.3 as the further-away future moved into 2.8.4 plan)

Point release to address tickets in general, and possible 2.8.0 fallout and 2.7.5 planned remainders that were not addressed in 2.8.1/2.8.2.

  • (expected) clean-up of basic data types usage (NUT string API and notably methods for numeric conversions, booleans, ...)
  • (expected) clean-up of libusb API variants support [#300 and follow-ups]
  • (expected) CI automation for coding style (clang-format)
  • (expected) CI automation for use of data points in drivers that conform to patterns defined in docs/nut-names.txt
  • (expected) Porting of performance and bug fixes from 42ITy project
  • (expected) Bug fixes for fallout possible due to "fightwarn" effort in 2.7.5/2.8.0 - a few were caught in 2.8.1 and 2.8.2
  • (expected) Basic C/C++ code built for WIN32 getting on par with POSIX as much as possible (many ifdefs now skip the higher-hanging fruit)
Loading