MB-8663 Add an entry to CHANGES file about XDCR settings.

Change-Id: I77ba4992a6febb7db23eb1cf172a8acefb5e6d37
Reviewed-on: http://review.couchbase.org/28552
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-8909 make errors for bucket password beautyful

without hardcoding width in html

Change-Id: I14a72cdd9d06a1edd3fbc4d4de53cd5f6e2fb4bb
Reviewed-on: http://review.couchbase.org/28541
Tested-by: Artem Stemkovski <artem@couchbase.com>
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-100 Don't crash if Min of Max is not an integer.

The can also be an atom infinity.

Change-Id: I734c6fa6bf1c646651211bb85214a98ae9130162
Reviewed-on: http://review.couchbase.org/28551
Tested-by: Aliaksey Artamonau <aliaksiej.artamonau@gmail.com>
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-8958: identify 2.2.0 "for xdcr" bucket list requests

In future we might plan to evolve bucket details response to remove
saslPassword field particularly. But that field is used by xdcr (xmem
mode). In order to be able to remove that field without breaking xdcr
backwards compatibility we'll start passing unused http query option.
So that future version can identify 2.2.0 requests and send it
saslPassword field as expected.

Change-Id: I0eddfef807310a2066348a97f5b3a3da785b2a5d
Reviewed-on: http://review.couchbase.org/28540
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Reviewed-by: Aliaksey Artamonau <aliaksiej.artamonau@gmail.com>
MB-100: use rep_details to check replication mode

Today in vb replicator we use xmem_srv process to check the mode
of replication, which is correct in most cases except that if it
crashed, the terminate function of vb replicator will not be able
to know which mode the vb replicator is using. Actually we have
already encoded replication mode info in rep_details, thus we
should use it instead of relying on xmem_srv process.

Change-Id: I22816e3cea5f478f699cd47940a67688d76114e5
Reviewed-on: http://review.couchbase.org/28561
Tested-by: Junyi Xie <junyi.couchbase@gmail.com>
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-8663 Mention where to find replication id.

Change-Id: I1902d5d04ee6ab020c7df491b86b3c9889e64da3
Reviewed-on: http://review.couchbase.org/28584
Reviewed-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
MB-8966: correctly fetch global settings for XDCR UI

Previous code fetched global settings even before current replication
setting url is set.

Correct behavior is making sure we fetch both global and
per-replication settings every time we are refreshing it.

Change-Id: I02a715761bc0f9a4a8a42815c0f8befc454e3d9f
Reviewed-on: http://review.couchbase.org/28585
Tested-by: Aliaksey Kandratsenka <alkondratenko@gmail.com>
Reviewed-by: Aliaksey Artamonau <aliaksiej.artamonau@gmail.com>
Tested-by: Aliaksey Artamonau <aliaksiej.artamonau@gmail.com>
Merge remote-tracking branch 'couchbase/2.2.0'

* couchbase/2.2.0:
  MB-8966: correctly fetch global settings for XDCR UI
  MB-8663 Mention where to find replication id.
  MB-100: use rep_details to check replication mode
  MB-8958: identify 2.2.0 "for xdcr" bucket list requests
  MB-100 Don't crash if Min of Max is not an integer.
  MB-8909 make errors for bucket password beautyful
  MB-8663 Add an entry to CHANGES file about XDCR settings.

Change-Id: Ice7267af488b33208980a796f964edbe8c5d8e3d