Yesterday we pushed build 2649 to our production servers. Several hours later we have discovered a serious issue with our usage of RavenDB that caused it to run out of internal storage sessions.
We believe that we found the root cause for this issue, and we pushed an update to that (build 2652). We will continue to monitor our production system, but assuming no further issues, I think we will give it a few more days in the real world before calling it stable.
Early next week we intend to re-run the entire stress test suite, so that would also increase our confidence in this build.
I encourage all of you to take RavenDB 2.5.2652 for a test run and report your finding to the list.