You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@couchdb.apache.org by ra...@apache.org on 2012/02/21 08:13:40 UTC
[32/50] git commit: clean up wording
clean up wording
git-svn-id: https://svn.apache.org/repos/asf/couchdb/site/htdocs@989943 13f79535-47bb-0310-9956-ffa450edef68
Project: http://git-wip-us.apache.org/repos/asf/couchdb/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb/commit/b5f87f03
Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/b5f87f03
Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/b5f87f03
Branch: refs/heads/htdocs
Commit: b5f87f03bb8d032524eb42bc5f5d88e2bfe4f632
Parents: 9591460
Author: Jan Lehnardt <ja...@apache.org>
Authored: Thu Aug 26 21:39:27 2010 +0000
Committer: Jan Lehnardt <ja...@apache.org>
Committed: Thu Aug 26 21:39:27 2010 +0000
----------------------------------------------------------------------
notice/1.0.1.html | 20 ++++++--------------
notice/1.0.1.txt | 20 ++++++--------------
2 files changed, 12 insertions(+), 28 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/couchdb/blob/b5f87f03/notice/1.0.1.html
----------------------------------------------------------------------
diff --git a/notice/1.0.1.html b/notice/1.0.1.html
index 7a7b649..d495127 100644
--- a/notice/1.0.1.html
+++ b/notice/1.0.1.html
@@ -80,27 +80,19 @@ limitations under the License.
<p><div style="border:5px dashed #F00;padding:1em"></p>
-<p><strong>A REPAIR TOOL IS NOW AVAILABLE</strong></p>
+<p><strong>A 1.0.0 RECOVERY TOOL IS NOW AVAILABLE</strong></p>
-<p>Download the <a href="http://wiki.couchone.com/page/repair-tool#/">CouchDB 1.0.0 Repair Tool</a> if you want to recover your data.</p>
+<p>Download the <a href="http://wiki.couchone.com/page/repair-tool#/">CouchDB 1.0.0 Repair Tool</a> to recover data.</p>
<p></div></p>
-<h2>Warning</h2>
+<h2>Notes on a Nasty Bug</h2>
-<p>If you are using CouchDB 1.0.0 and have the default setting for ‘delayed_commits’ (true) then you are affected by this data loss bug. You should read this page very carefully and apply the remedy as soon as practicable.</p>
+<p>Developers should be using 1.0.1 release only at this point; not the 1.0.0 version. Read on to find out why.</p>
-<p>This bug does not affect earlier releases of CouchDB.</p>
+<p>On the weekend of August 7th–8th, 2010 we discovered and fixed a bug in CouchDB 1.0.0. The problem was subtle (cancelling a timer, without deleting the reference to it) but the ramifications were not: there was potential data loss for users of 1.0.0. The 1.0.1 release contains a permanent fix, and <a href="../downloads.html">is available now on the download page</a>.</p>
-<p>Even if you have lost data due to this bug it is possible that it can be recovered. If you can, archive a copy of the database that has lost data, if not, at least do not compact your databases as the repair tool will not be effective if you do so. Please subscribe to the <a href="http://couchdb.apache.org/community/lists.html">user@ or dev@ mailing list</a> to get notified when the tool will be available.</p>
-
-<h2>Post mortem for a nasty bug</h2>
-
-<p>Over the weekend of August 7th–8th, 2010 we discovered and fixed a nasty bug in CouchDB 1.0.0. The problem was subtle (cancelling a timer, without deleting the reference to it) but the ramifications are not: <strong>once the bad code path is triggered, subsequent writes to the database are never committed.</strong> This means there is potential data-loss for users of 1.0.0.</p>
-
-<p>Luckily, triggering the bad code path doesn’t happen to everyone, and there is a hot fix that can prevent data loss (as long as it is applied before the server is restarted or crashes.)</p>
-
-<p>The 1.0.1 release will contain a permanent fix, and is expected this week. For now, this article will explain how to achieve data-safety on CouchDB 1.0.0. We will also look at the bug itself, how it happened, and what we are doing to prevent something similar happening again.</p>
+<p>We are proud how quickly the CouchDB community recovered from this bug and went the extra mile to make sure everyone’s data was safe. It is clear we have a group of developers who care enough about all users’ data that it aggressively pursued an “edge case” bug so no one would be caught off guard. Further, the team worked for the next week to create a repair tool to recover access to data which was affected by the bug. As a result, no users lost data permanently. Kudos!</p>
<h2>The Remedy</h2>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/b5f87f03/notice/1.0.1.txt
----------------------------------------------------------------------
diff --git a/notice/1.0.1.txt b/notice/1.0.1.txt
index f67d004..e23bb90 100644
--- a/notice/1.0.1.txt
+++ b/notice/1.0.1.txt
@@ -5,27 +5,19 @@ Sort-Index: 061
<div style="border:5px dashed #F00;padding:1em">
-**A REPAIR TOOL IS NOW AVAILABLE**
+**A 1.0.0 RECOVERY TOOL IS NOW AVAILABLE**
-Download the [CouchDB 1.0.0 Repair Tool](http://wiki.couchone.com/page/repair-tool#/) if you want to recover your data.
+Download the [CouchDB 1.0.0 Repair Tool](http://wiki.couchone.com/page/repair-tool#/) to recover data.
</div>
-## Warning
+## Notes on a Nasty Bug
-If you are using CouchDB 1.0.0 and have the default setting for 'delayed_commits' (true) then you are affected by this data loss bug. You should read this page very carefully and apply the remedy as soon as practicable.
+Developers should be using 1.0.1 release only at this point; not the 1.0.0 version. Read on to find out why.
-This bug does not affect earlier releases of CouchDB.
+On the weekend of August 7th–8th, 2010 we discovered and fixed a bug in CouchDB 1.0.0. The problem was subtle (cancelling a timer, without deleting the reference to it) but the ramifications were not: there was potential data loss for users of 1.0.0. The 1.0.1 release contains a permanent fix, and [is available now on the download page](../downloads.html).
-Even if you have lost data due to this bug it is possible that it can be recovered. If you can, archive a copy of the database that has lost data, if not, at least do not compact your databases as the repair tool will not be effective if you do so. Please subscribe to the [user@ or dev@ mailing list](http://couchdb.apache.org/community/lists.html) to get notified when the tool will be available.
-
-## Post mortem for a nasty bug
-
-Over the weekend of August 7th–8th, 2010 we discovered and fixed a nasty bug in CouchDB 1.0.0. The problem was subtle (cancelling a timer, without deleting the reference to it) but the ramifications are not: **once the bad code path is triggered, subsequent writes to the database are never committed.** This means there is potential data-loss for users of 1.0.0.
-
-Luckily, triggering the bad code path doesn't happen to everyone, and there is a hot fix that can prevent data loss (as long as it is applied before the server is restarted or crashes.)
-
-The 1.0.1 release will contain a permanent fix, and is expected this week. For now, this article will explain how to achieve data-safety on CouchDB 1.0.0. We will also look at the bug itself, how it happened, and what we are doing to prevent something similar happening again.
+We are proud how quickly the CouchDB community recovered from this bug and went the extra mile to make sure everyone's data was safe. It is clear we have a group of developers who care enough about all users' data that it aggressively pursued an "edge case" bug so no one would be caught off guard. Further, the team worked for the next week to create a repair tool to recover access to data which was affected by the bug. As a result, no users lost data permanently. Kudos!
## The Remedy