speaking as mainly an mpc100 user "stability" then is a matter of semantics, the bug fixes were not to correct show stopping crashes or huge losses of work ( akin to the akai unfinished/unpaid for/unscrupulous os) but minor work flow irritations. yes some pieces of data were lost, and yes they needed to be fixed... and they were.
some "stability" issues mentioned here are really "user forgot to press the erase key after re-installing issues"
others mention "stability" but dont trace there steps to work out what caused it to produce accurate bug reports.(one reason why os1 and os 2 have eventually far exceeded the akai os's standard of "stability", even with all the extra features)
and of course there are genuine bugs :
----------------------------------------------
Bug Fixes: OS2XL Ver1.25 31-MAR-2010
---------------------------------------------
1. [TIMING CORRECT WINDOW]
If an ALL track is performed by timing correction, the event of other tracks currently recorded
on the same location as a track 1 will be erased.
2. [DRUM GRID]
[VIEW]
The event recorded by 1/16-3 may be erased.
3. [ERASE WINDOW]
A REAL TIME event cannot be erased.
4. [MIXER]
Screen of F5 (INPUT) is not memorized.
" lack of stability " then seems a more apt description for the early stages of os1,2 and xl and most notoriously the
original akai os