<commit_before># Release Notes

This document is a list of user visible feature changes and important
bugfixes. Do not forget to update this doc in every important patch.

## 1.3.12 (2015-04-21)

* [major] Experimental support of N1QL querires

## 1.3.11 (2015-01-08)

* [minor] Update crossbuild system to use cmake for libcouchbase

* [minor] Update to libcouchbase 2.4.5 and wire IO functions at
  runtime

## 1.3.10 (2014-09-30)

* [major] Updates regarding libcouchbase 2.4.2. Bundle "bsdio-inl.c"
  which is not part of libcouchbase distribution anymore. This fixes
  installation recent ruby gem versions with libcouchbase 2.4.2.

* [minor] Allow both `:hostname` and `:host` options to constructor

## 1.3.9 (2014-08-26)

* [major] Updates regarding libcouchbase 2.4.0. Deprecations cleanup

## 1.3.8 (2014-06-11)

* [major] RCBC-176 Known Issue: When the couchbase client is used in
  an 'em-synchrony' context, it is possible that connection errors may
  not be propagated to the client. This leads to runtime assertion in
  eventmachine.<commit_msg>Update release notes<commit_after># Release Notes

This document is a list of user visible feature changes and important
bugfixes. Do not forget to update this doc in every important patch.

## 1.3.13 (2015-05-16)

* [major] RCBC-196 Improved integration with libcouchbase IO API

## 1.3.12 (2015-04-21)

* [major] Experimental support of N1QL querires

## 1.3.11 (2015-01-08)

* [minor] Update crossbuild system to use cmake for libcouchbase

* [minor] Update to libcouchbase 2.4.5 and wire IO functions at
  runtime

## 1.3.10 (2014-09-30)

* [major] Updates regarding libcouchbase 2.4.2. Bundle "bsdio-inl.c"
  which is not part of libcouchbase distribution anymore. This fixes
  installation recent ruby gem versions with libcouchbase 2.4.2.

* [minor] Allow both `:hostname` and `:host` options to constructor

## 1.3.9 (2014-08-26)

* [major] Updates regarding libcouchbase 2.4.0. Deprecations cleanup

## 1.3.8 (2014-06-11)

* [major] RCBC-176 Known Issue: When the couchbase client is used in
  an 'em-synchrony' context, it is possible that connection errors may
  not be propagated to the client. This leads to runtime assertion in
  eventmachine.
{'fraction_non_alphanumeric': 0.09291835814163284, 'fraction_numerical': 0.07352277852954443, 'mean_word_length': 3.928888888888889, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3061821', 'n_tokens_mistral': 828, 'n_tokens_neox': 709, 'n_words': 287}