I realize that when I used the phrase “
bug fix” in my previous post, it’s probably tempting to understand that as “
fix all known and reported issues”, but in reality - it’s not that simple. Companies categorize bugs by their impact and importance, and select which to fix in each release (if at all). I looked, but couldn’t find a comprehensive list of issues that are slated for the upcoming SP3000 series FW release, nor do the prior FW releases itemize all fixes.
Here’s a general hierarchy of how fixes are categorized:
- Critical: issues that cause major crashes, complete system failure, or completely break core functionality; severe security vulnerabilities
- High: issues that may impact core functionality but workarounds or reduced quality of service exist; less severe security vulnerabilities
- Medium: issues to minor functionality, workarounds may or may not exist, issues may be cosmetic; non-severe security issues
- Low: minor issues, might annoy some users but impact to overall functionality is very low; may never be fixed
A&K will likely continue to slow SP3000 series FW releases, while almost assuredly narrowing focus to
critical and
high priority fixes only. Owners should expect 6-12+ months between FW releases as long as active support lasts, as that’s the standard set by A&K for products in this lifecycle stage and for non-critical/not high priority fixes. Not all bugs will be fixed (that’s not feasible).
Also keep in mind that while a customer might class a specific bug as “
critical” or “
high”, it’s likely not getting that designation from the product team at A&K. As an example, the LED sometimes illuminating the wrong color would almost certainly fall into
medium or
low.