From 77b23886dda16b5e12d2fd8256bdd5b3ab99c4a9 Mon Sep 17 00:00:00 2001 From: Bob Grabar Date: Wed, 5 Sep 2012 12:09:09 -0400 Subject: [PATCH] DOCS-390 release notes integration --- source/installation.txt | 2 +- source/release-notes.txt | 3 ++- {draft => source}/release-notes/2.0-changes.txt | 0 {draft => source}/release-notes/2.0.txt | 4 ++-- 4 files changed, 5 insertions(+), 4 deletions(-) rename {draft => source}/release-notes/2.0-changes.txt (100%) rename {draft => source}/release-notes/2.0.txt (99%) diff --git a/source/installation.txt b/source/installation.txt index ba56d8bde2e..6b19c3884aa 100644 --- a/source/installation.txt +++ b/source/installation.txt @@ -35,7 +35,7 @@ while v2.1 and v2.3 is a development version. - Previous Stable Releases - - :wiki:`v2.0 Release Notes <2.0+Release+Notes>` + - :doc:`/release-notes/2.0` - :wiki:`v1.8 Release Notes <1.8+Release+Notes>` - Current Development Release (v2.3-series) diff --git a/source/release-notes.txt b/source/release-notes.txt index 22572dc796c..769266c5e56 100644 --- a/source/release-notes.txt +++ b/source/release-notes.txt @@ -19,5 +19,6 @@ in 2.2. Previous stable releases: -- :wiki:`v2.0 Release Notes <2.0+Release+Notes>` +- :doc:`/release-notes/2.0` + - :wiki:`v1.8 Release Notes <1.8+Release+Notes>` diff --git a/draft/release-notes/2.0-changes.txt b/source/release-notes/2.0-changes.txt similarity index 100% rename from draft/release-notes/2.0-changes.txt rename to source/release-notes/2.0-changes.txt diff --git a/draft/release-notes/2.0.txt b/source/release-notes/2.0.txt similarity index 99% rename from draft/release-notes/2.0.txt rename to source/release-notes/2.0.txt index b82f69c9664..c41e952417a 100644 --- a/draft/release-notes/2.0.txt +++ b/source/release-notes/2.0.txt @@ -111,7 +111,7 @@ See :issue:`SERVER-2563` for more information. The specific operations yield in 2.0 are: -- Updates by _id +- Updates by ``_id`` - Removes @@ -155,7 +155,7 @@ Priorities Each :term:`replica set` member can now have a priority value consisting of a floating-point from 0 to 1000, inclusive. Priorities let you -control which member of the set you prefer to have as :term:`primary`: +control which member of the set you prefer to have as :term:`primary` the member with the highest priority that can see a majority of the set will be elected primary.