Quote:
Originally Posted by chaley
My intention would be to make intermediate releases to the alpha group once I have new functions/change that are internally tested. These releases might happen once a week, faster if comments call for it, slower if I am feeling lazy or traveling.
The beta group would get releases a week or two before I intend to make a general release, which generally happen every three months or so. The hope is that the beta releases are very close to production, and because of that I will be much less willing either to add new functionality at that point or to change them for anything that isn't a bug. Of course, the definition of "bug" is mutable.
a_daley's comment about backups is a good one. There is no guarantee that one can revert to an older release without doing a total uninstall. Reasons: releases change both the database structure and the meaning of settings, and reverting won't revert those changes. In general, doing a CC settings backup before upgrading will suffice unless there is also a database upgrade, but I can't guarantee this. And it is worth noting that this has always been true for prereleases. Having an alpha group won't change that.
|
If you use Titanium Backup it can restore even db changes if you restore app + data. I would do the alpha group if you have one. I do weekly backups so I wouldn't lose a lot even if I did revert.