Mike, please take a look at the the Release Notes link provided by JM in his post originating this thread. In particular, see the notes regarding beta to beta upgrade breakage in build 260 due to major changes that have been made to improve the product and resolve open bugs. Also, at this same URL, you will find (at the bottom) the full list of resolved 3.0 bugs, and the list of known open bugs as of the date of this release.
260 is significantly improved over 236 in both appearance (UI changes), and working features (closed bugs). Since neither release is considered production ready as a beta, you will have to evaluate the worth of redeployment in your test environment based on your own interest and needs. We would certainly welcome your continued participation in the beta, but would understand if you chose to wait for a release candidate or final release.
