http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660@Moti, we will start with an upgrade on Monday, 2/18/2013 & will move out of Beta shortly after. After we move out of beta support for V2, we will be hardening our upgrade schedule for V2 releases to what we supported in 960. This includes upgrading to stable releases after doing our own regression testing. Our release schedule has historically been between 2 weeks to 1 month after the release of a stable build. As always, customers on replicated plans won't experience any downtime during these upgrades. http://ayende.com/161122/ravendb-2-01-stable-release#comment11http://ayende.com/161122/ravendb-2-01-stable-release#comment11Wed, 13 Feb 2013 18:53:18 GMTThere is no excuse for upgrading a production system without attempting an upgrade in a staging environment first. There is a plan to use the 2.0 version and that plan involves the use of a staging area.http://ayende.com/161122/ravendb-2-01-stable-release#comment10http://ayende.com/161122/ravendb-2-01-stable-release#comment10Tue, 12 Feb 2013 03:29:34 GMTJoão, Yes, a 2.01 client should work with 2.0 server and vice versa.http://ayende.com/161122/ravendb-2-01-stable-release#comment9http://ayende.com/161122/ravendb-2-01-stable-release#comment9Sun, 10 Feb 2013 09:17:01 GMTOren, can you tell us how ravenhq plan to handle those minor releases? http://ayende.com/161122/ravendb-2-01-stable-release#comment8http://ayende.com/161122/ravendb-2-01-stable-release#comment8Fri, 08 Feb 2013 19:28:37 GMTWill the existing 2230 client work with server 2261?http://ayende.com/161122/ravendb-2-01-stable-release#comment7http://ayende.com/161122/ravendb-2-01-stable-release#comment7Fri, 08 Feb 2013 17:22:41 GMTI've upgraded to 2.01 (2261) and we are loving it. I highly recommend you upgrade. This is a MUCH more mature, high-quality product than 1.0. @Arne - as a paying customer, you should easily be able to get support. Even if you're on the FOSS license - the community forum support is quite responsive. My guess is that you hit on some of the issues with m/r indexes that are pointed out in this article. Several of those I tested myself, confirmed broken, and then confirmed fixed with the new release. I suggest you try 2.01 in a test environment with a copy of your production data. If you still have issues, please report them. If not, then you can reconsider it for production. Peace.http://ayende.com/161122/ravendb-2-01-stable-release#comment6http://ayende.com/161122/ravendb-2-01-stable-release#comment6Fri, 08 Feb 2013 17:16:40 GMTArne, We have _really_ good support channels, and this is the first time that I have heard about this. If you have a db corruption, pretty much the first thing that you need to do is call the vendor. We could have helped you get things working again. http://ayende.com/161122/ravendb-2-01-stable-release#comment5http://ayende.com/161122/ravendb-2-01-stable-release#comment5Fri, 08 Feb 2013 15:08:05 GMTClassic example of “if it isn’t broken don’t fix it”. Sorry to hear about your issues but that is the price you pay for “just upgrading” for no reason (unless you had a serious issue with the current system or there is a feature that is a must) why would you just upgrade a production system so casually? http://ayende.com/161122/ravendb-2-01-stable-release#comment4http://ayende.com/161122/ravendb-2-01-stable-release#comment4Fri, 08 Feb 2013 15:02:44 GMTAs I said we fixed it with export/import. My biggest concern is to keep our site up and running. We had around 15minutes of downtime. I experienced data corruption around a year ago too. I reported this to the support form on the web page and never got a response. My patience is only so big.http://ayende.com/161122/ravendb-2-01-stable-release#comment3http://ayende.com/161122/ravendb-2-01-stable-release#comment3Fri, 08 Feb 2013 14:59:08 GMT@Arne: If you suffered database corruption for weeks why didn't you report this problem to Hibernating Rhinos? I'm no customer but I got the impression that Oren and his team do everything in their power to help customers as quickly as possible, especially when it comes to urgent matters like data corruption. Trash talking products without getting support involved at first isn't very nice. In fact it's kind of rude. http://ayende.com/161122/ravendb-2-01-stable-release#comment2http://ayende.com/161122/ravendb-2-01-stable-release#comment2Fri, 08 Feb 2013 14:31:41 GMTWe upgraded to 2.0 last week. Next day our RavenDB database got corrupt. This caused our production web site to crash. We had to export/import the database to get it up and running again. Who knows what caused it and if it may happen again in the future. Then our map/reduce indexes started to get corrupt at least once a day. We have to manually reset the indexes a couple of times a day to make them work. The business side that consumes the report based on the map/reduce indexes is now losing faith in the reports and our system. Lastly adding the count of each document collection in Raven Studio does not add up to the total document count shown in the bottom. Which one is correct? The diff is just a couple of hundred of documents... Right now i am really frustrated and i regret that we chose RavenDB for our production system. It's good that you fix all these bugs in this release, but the problem is that it is two weeks too late for us. To keep your clients happy you have to improve the quality of your product. As a database user I want to be 100% sure that my data is correct and secure at all times. The users are making business decisions based on your product!http://ayende.com/161122/ravendb-2-01-stable-release#comment1http://ayende.com/161122/ravendb-2-01-stable-release#comment1Fri, 08 Feb 2013 12:14:17 GMT