Roger Vellacott wrote:

> So we have a dilemma. Should we update all our clients to an "unstable"
> release, with the theoretical possibility that it contains other errors,
> or should we just hope there are not too many more database corruption
> incidents before the release of 2.1.3?

IHMO, you should simply go back to previous stable release, 2.1.1.

> But if it is a rule that nothing can be released unless it has been
> fully tested, and has gone through a final "perfect" RC phase with zero
> changes, then this is a degree of perfectionism which may be detrimental
> to the reliability of the product that people are actually using.

Maybe FB team should have revoked 2.1.2 release, as was already suggested.


--
Milan Babuskov
http://www.flamerobin.org
http://www.guacosoft.com