Quote:
Originally Posted by jackie_w
Regarding alpha vs beta. In principle I'm happy to be in an alpha group if all I need to worry about is backing up CC's settings before I start. If I need to be rooted and do full system backups to protect my other Android apps, then I'll need to stick with the beta group. Low-level Android tinkering is outside my comfort zone.
|
In my two years of developing CC I have never had a case where I had to do a system restore. I also have never had a case where CC's database was destroyed.
What I have had happen:
- mistakes where I messed up migrating preferences to the point where regenerating them from scratch was easier than trying to fix them. A preferences backup will take care of that, and in any event I don't think it is likely that I would release something that did this.
- changes to the database that didn't work out. One deficiency of SQLite, the db used by Android and lots of other SW including calibre, is that there is no way to undo changes that added information to the db. The easiest way to fix these is to reinitialize (clear data). This has happened 3 or 4 times, and never in a prereleased CC.
My intention is to release features as I build them and after I have tested them instead of holding them in abeyance for the period just before the production release. The risk of corruption should be low. On the other hand, it could be that the community decided that the way I did it isn't optimal, and correcting it might be best done with a reload, although I think this would be extremely rare. Hasn't happened yet.
Waiting a few days for other
masochists alpha testers report is not a silly idea. I think doing that reduces risks to more than acceptable levels. Of course, if *everybody* waits then it doesn't, but that won't happen.
