Sansa Clip ZIP: Rockbox build -- how unstable is "unstable"

[mcc01]

Hi,

I compared the sansaclipzip.h of the stable release and the current snapshot and found
some change which indicate settings based on more experience with the Clip ZIP as there
were at time of the stable release.

On the other hand I dont want to be on an fsck.fat-party (I am non Linux)
each day, because the mplayer goes to nirwana again I have to do a
hard reset which results often in a damaged FAT.

Since I have experienced a wide range of the meaning of "unstable"
in the OpenSource community (NO OFFENSE INTENDED!!!) I want to
ask how "unstable" is defined in the rockbox community especially
in concern to the Sansa Clip ZIP.

How unstable is "unstable" ?

Best regards,
mcc

[gevaerts]

How unstable is "unstable" ?

In rockbox, "unstable" tends to mean "There are lots of changes" (although this used to be more true than it is today, development has slowed down...) rather than "It crashes all the time"

[mcc01]

Hi gevaerts,

thanks for the einformation!

I have to correct my previous post:
I wrote
"On the other hand I dont want to be on an fsck.fat-party (I am non Linux)..."
it must be
"On the other hand I dont want to be on an fsck.fat-party (I am on Linux)..."
...not to contradict myself with others posts I send to this forum...

Best regards,
mcc

[Astrogoth]

At the moment it means when you plug a USB cable into the ZIP you MUST pause before you plug or the ZIP's OS will crash with a white screen and require a long press of the power button to fix it. That's the only obvious bug I've seen and that's only been around for the last few months.