I've been on the latest beta since it came out... on the module that is... no problems with it, exept I believe that it has a problem with program changes when using it in multi mode... the OS is probably one of DSI's least buggy in my opinion.
And regarding doing an update... really... it's no big deal... people often get scared, that IF a dump goes wrong, then hell breakes loose and you are good with a door stopper.
That is NOT the case...
First of... the SysEx dump has a checksum in it... this checksum is recalculated once P8 has recieved the OS, and if it does not match the checksum stored in the dump, then it'll tell you, and not write the OS to flash...
If the checksum matches, P8 will write the OS into flash... this is done without any interference from the computer... it's solely a job for the P8 alone... if that fails for some reason, or you switch off P8 while it's doing it, THEN you'll have a damaged OS...
But even if that happens, you can initiate an OS update by doing a special key combination at power up... the code for doing the update is not part of the OS itself... thus, this "boot code" can be initialized by this button combi, and you can resend the OS, and have it burn the OS to flash again... you can keep on doing that until it works.
The only way to get a bricked P8 is if this boot-code that writes the OS is somehow damaged... but as this is not updated thru an OS update, it should not be possible for it to happen.
I've updated every DSI synth I've got this far... Mopho, Tetra, Desktop Evolver, Mono Evolver Keyboard, Poly Evolver Rack, Prophet 08, Prophet 12 and Tempest... NONE has failed... not even once... and I update as soon as a new OS is out, all the time, so we're talking MANY updates.
If you just follow the info given with an OS update, I'd say there is a greater chance to get killed in traffic, than an OS update error that'll brick your synth.