Beta 1 was posted (very) late Sunday night and reaction has been very positive overall. It's probably the most stable and problem-free build over all as well, which is good because a lot of people downloaded it and have started using it for the first time. The only major problem that was discovered is with unlocking an encrypted journal with an incorrect password causes a crash. For those developers out there, goto-ing past a variable declaration is bad! But this has been fixed for the next build. As soon as I can manage it, I'll have a localization kit out there and we'll start folding in updated localizations into new builds. Builds from this point will only have bug fixes and new localizations in them; any new features will have to wait for the as-yet-unnumbered next release. As always, you can use the "Report A Bug" menu item in the Help menu to get the most up-to-date listing of known issues in whatever build you have.
Another thing I started doing from the first alpha of 2.6 is expiration dates. Using old builds is a Bad Idea, so they have a hard expiration date of 60 days after release when they will refuse to launch. I have gotten e-mails from people using development builds of 2.5 more than a year after it was released, so this is a way to prevent this. In general, you always want to be on the latest build, but usually the releases are scheduled so a few builds can work at once just in case. I think alpha 5 is expired, but everything after that still works. Please let me know if there's a reason that you can't move to a newer build so it can be fixed before your build expires.