We’re happy to announce the release of Couchbase Server 3.0.3 Enterprise Edition. As many of you may know, the 3.0 was significant release for the company and had many architectural changes also introduced several exciting features like tunable memory and, encrypted data access that provided better reliability and security for enterprises.
The focus of the 3.0.3 release is to fortify the 3.0 releases further by addressing feedback provided by our users and customers, specifically fixing reliability issues with Database Change Protocol (DCP). The full release notes are available here.
You can download and check-out the latest version on our download page. If you are currently running Couchbase Server 3.0/3.0.1/3.0.2 EE, we recommend that you upgrade to version 3.0.3 EE. We are working on the community edition and will update our download page once available.
Try out 3.0.3 and give us your feedback!
What are the plans for the community edition?
We are planning on releasing Couchbase Server 4.0 in a few months with a developer preview coming in the next few weeks. Our plan is, 4.0 will have a community edition that community can use to take advantage of advanced queries with SQL for Documents (a.k.a N1QL).
Any plans for a community edition of 3.0.3 specifically?
Hi Ben, Community edition follows a few months behind so a new community edition isn\’t imminent.
So basically you\’re lying to your customers, and have no intention of supporting a community edition in good faith? As of June 15th, 2015 the Couchbase site reads: \”Bug fixes and new features are eventually integrated with the Community Edition (CE), but this typically takes several weeks. \”
Thanks Franklin, it’s not a question of trying to be unfaithful to what we say, it’s just that the text as written there is a bit overly optimistic on the release cycle. I will work to correct that text.
The idea is that there are certain points where we cut a CE release that rolls up fixes. For those who need the most up to date fixes and the ability to prioritize fixes, there are EE subscriptions.
Right around now the effort is on 4.0 which we’re working to get to GA. That’ll have a CE release with rolled up fixes along with the new features. Since we’re between bigger releases, the time distance is longer than a few weeks. That’s why we need to update that text to be more inline with this particular set of circumstances in our release cycle.
All of Couchbase is Open Source under the Apache 2.0 license and you can find it at http://github.com/couchbase. Of course, anything you build there wouldn’t be a release (either CE or EE) by Couchbase— it’d be your own build.
Do you realize that due to a bug in 3.0.1 no one using the community edition of Couchbase can backup or restore their data? Even worse is you have a fix in 3.0.3 yet refuse to release it to the CE. How can Couchbase justify focusing on Version 4 when version 3 is not stable (backing up and restoring)? How could anyone running couchbase 3.0.1 CE upgrade to 4 since they can not backup their data?
This is what I hear you saying: \”we don\’t plan on releasing 3.0.3 as a community edition, if you have a problem with this, then pay for the EE, or wait for the 4.0 version, or fix the problem yourself. Be advised that the community edition is not a priority and has no promise of quality from Couchbase.\”
If this represents the attitude of Couchbase as a whole, then I recommend the company stop pretending to be an open source friendly company and just charge money for Couchbase. Microsoft is a good company to model in this realm.
I agree, this is a real issue, not an inconvenient little bug, The issue is causing rebalancing, backup and transfer of data to fail. All I can say is that the admin side of couchbase is worse than horrible, and I for one will not be recommending it to any other projects.
Thanks for the feedback and I do understand the frustration. To be crisp; Are you guys referring to this issue: https://issues.couchbase.com/b…
the issue you are pointing at (https://issues.couchbase.com/b… is an issue on couchbase server 4.0 (codenamed sherlock). I assume your comments were based on 3.0.1. If you can reproduce this issue in 3.0 pls let me know. You likely already know that 4.0 is still in development and is not supported in production deployments). – Instead we have a few reports of issues on cbbackup that is being tracked here: https://issues.couchbase.com/b… – this issue impacts all 3.x versions regardless of edition. We have a workaround we documented in the JIRA ticket. If you can try the workaround and let me know the outcome it would be great. I can be reached at firstname.lastname@example.org.
For the forum threads, I replied with posts to threads to ensure all folks are aware of the workaround to the cbbackup issue.
You can add one line to the Python script to fix the backup/restore issue: https://issues.couchbase.com/b…