List view

• 2.8.3

  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 libusb API variants support [#300 and follow-ups] - (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

  No due date

  •350/351 issues closed
  99% complete1 open350 closed

• 2.8.2

  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. - Bug fixes for fallout of work done in 2.8.0/2.8.1 - Porting of some features from 42ITy project - CI/build-recipe improvements

  No due date

  •131/132 issues closed
  99% complete1 open131 closed

• 2.8.1

  Point release primarily to address possible 2.8.0 fallout, and possibly some tickets in general and/or 2.7.5 planned remainders (unfinished goals can go to 2.8.2+): - (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

  No due date

  •327/327 issues closed
  100% complete0 open327 closed

• 2.8.0

  Half a decade worth of improvements since 2.7.4, many new drivers, refactoring for clean warnings-less code, as well as some new key words for configuration and protocol (server and client should be backwards-compatible, but configuration files using new features would not be understood by older daemon builds - hence 2.8.x).

  No due date

  •73/74 issues closed
  98% complete1 open73 closed

• 2.7.4

  No due date

  •22/22 issues closed
  100% complete0 open22 closed

• 2.7.3

  An 3rd achievable short term goal... to ramp-up toward 2.8.0

  No due date

  •20/20 issues closed
  100% complete0 open20 closed

• 2.7.2

  An 2nd achievable short term goal... to ramp-up toward 2.8.0

  No due date

  •14/14 issues closed
  100% complete0 open14 closed

• 2.7.1

  An achievable short term goal...

  Due by July 7, 2013

  •8/8 issues closed
  100% complete0 open8 closed