Only New Bugs Fixed?
Posted: Thu Aug 19, 2021 10:44 pm
1) Bug fixes in last 12 months: engine=113, ide=13. Stable releases in last 12 months: 3, LC v9.6.1 to LC v9.6.3.
(Aug20:v9.6.1 e=30/ide=1, Sep20:0, Oct20:0, Nov20:0, Dec20:0, Jan21:0, Feb21:0, Mar21:0, Apr21:0, May21:v9.6.2 e=39/ide=5, Jun21:0, Jul21:v9.6.3 e=44/ide=7, Aug21:0.) Is Quality Control now adequately staffed after Covid shutdown?
2) Bug fixes for LC v9.6.1 to LC v9.6.3 appear to be nearly all newer submissions. If so, what of confirmed older bugs and enhancement requests? Has Quality Control ever explained the criteria for choosing which bugs get fixed? Is there any prioritization other than crashes?
I may be naive, but I don't think giving up on older reports is good.
A) Search bug database to find old report and not make new report assuming old is in que. Result: no fix.
B) Add new findings to old report. Result: no fix.
C) Nag no fix yet to old report. Result: no fix.
D) Submit new bug report anyway, Quality Control flags as duplicate and merges with old report. Result: no fix.
3) A database search for "confirmed" at http://quality.livecode.com/ shows at least 500 confirmed bugs, newest bug 23295 confirmed 8-17-2021, oldest bug 12149 confirmed 4-15-2014.
This is disappointing. I get it at one level. New reports pile up as paying customers demand fixes, older bugs might get fixed with newer fixes, many reports are minor affecting only a few users who may no longer be active or care. LC Ltd is a private company and does what they want. Nothing I say will change that. We all know using the free Community version makes us beta testers. We volunteer time and effort to submit bug reports. Quality Control politely files them but has no obligation to fix.
(Aug20:v9.6.1 e=30/ide=1, Sep20:0, Oct20:0, Nov20:0, Dec20:0, Jan21:0, Feb21:0, Mar21:0, Apr21:0, May21:v9.6.2 e=39/ide=5, Jun21:0, Jul21:v9.6.3 e=44/ide=7, Aug21:0.) Is Quality Control now adequately staffed after Covid shutdown?
2) Bug fixes for LC v9.6.1 to LC v9.6.3 appear to be nearly all newer submissions. If so, what of confirmed older bugs and enhancement requests? Has Quality Control ever explained the criteria for choosing which bugs get fixed? Is there any prioritization other than crashes?
I may be naive, but I don't think giving up on older reports is good.
A) Search bug database to find old report and not make new report assuming old is in que. Result: no fix.
B) Add new findings to old report. Result: no fix.
C) Nag no fix yet to old report. Result: no fix.
D) Submit new bug report anyway, Quality Control flags as duplicate and merges with old report. Result: no fix.
3) A database search for "confirmed" at http://quality.livecode.com/ shows at least 500 confirmed bugs, newest bug 23295 confirmed 8-17-2021, oldest bug 12149 confirmed 4-15-2014.
This is disappointing. I get it at one level. New reports pile up as paying customers demand fixes, older bugs might get fixed with newer fixes, many reports are minor affecting only a few users who may no longer be active or care. LC Ltd is a private company and does what they want. Nothing I say will change that. We all know using the free Community version makes us beta testers. We volunteer time and effort to submit bug reports. Quality Control politely files them but has no obligation to fix.