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:41 UTC
[46/50] git commit: add data loss post mortem
add data loss post mortem
git-svn-id: https://svn.apache.org/repos/asf/couchdb/site/htdocs@983484 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/a419e8d1
Tree: http://git-wip-us.apache.org/repos/asf/couchdb/tree/a419e8d1
Diff: http://git-wip-us.apache.org/repos/asf/couchdb/diff/a419e8d1
Branch: refs/heads/htdocs
Commit: a419e8d1b81cb921661de1219b15e81b353dbc51
Parents: 654bdf5
Author: Jan Lehnardt <ja...@apache.org>
Authored: Sun Aug 8 21:23:19 2010 +0000
Committer: Jan Lehnardt <ja...@apache.org>
Committed: Sun Aug 8 21:23:19 2010 +0000
----------------------------------------------------------------------
community/code.html | 4 +
community/committers.html | 28 +++--
community/index.html | 4 +
community/issues.html | 4 +
community/lists.html | 20 ++--
docs/books.html | 4 +
docs/index.html | 4 +
docs/intro.html | 4 +
docs/overview.html | 4 +
downloads.html | 23 ++---
downloads.txt | 17 +---
index.html | 4 +
notice/1.0.1.html | 233 ++++++++++++++++++++++++++++++++++++++++
notice/1.0.1.txt | 138 ++++++++++++++++++++++++
notice/index.html | 98 +++++++++++++++++
notice/index.txt | 8 ++
screenshots.html | 4 +
security.html | 4 +
18 files changed, 557 insertions(+), 48 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/community/code.html
----------------------------------------------------------------------
diff --git a/community/code.html b/community/code.html
index 3686acf..483b165 100644
--- a/community/code.html
+++ b/community/code.html
@@ -69,6 +69,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/community/committers.html
----------------------------------------------------------------------
diff --git a/community/committers.html b/community/committers.html
index 4b77796..5bcb5a6 100644
--- a/community/committers.html
+++ b/community/committers.html
@@ -69,71 +69,75 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
<div id="content"><h1>Committers</h1>
-<p><a href="http://damienkatz.net/">Damien Katz</a>, <a href="mailto:damien@apache.org">damien@apache.org</a></p>
+<p><a href="http://damienkatz.net/">Damien Katz</a>, <a href="mailto:damien@apache.org">damien@apache.org</a></p>
<p>Original developer and Apache CouchDB PMC Chair.</p>
-<p><a href="http://jan.prima.de/">Jan Lehnardt</a>, <a href="mailto:jan@apache.org">jan@apache.org</a></p>
+<p><a href="http://jan.prima.de/">Jan Lehnardt</a>, <a href="mailto:jan@apache.org">jan@apache.org</a></p>
<p>Worked on the original UNIX port and now works on all ends in CouchDB.
He is a freelancing CouchDB consultant and gives presentations around the
world.</p>
-<p><a href="http://tumbolia.org/nslater">Noah Slater</a>, <a href="mailto:nslater@apache.org">nslater@apache.org</a></p>
+<p><a href="http://tumbolia.org/nslater">Noah Slater</a>, <a href="mailto:nslater@apache.org">nslater@apache.org</a></p>
<p>Developed and maintains the Autotools build system and application
infrastructure. He is CouchDB’s release manager and maintains a number of
related packages for Debian GNU/Linux.</p>
-<p><a href="http://www.cmlenz.net/">Christopher Lenz</a>, <a href="mailto:cmlenz@apache.org">cmlenz@apache.org</a></p>
+<p><a href="http://www.cmlenz.net/">Christopher Lenz</a>, <a href="mailto:cmlenz@apache.org">cmlenz@apache.org</a></p>
<p>Developed and maintains Futon, the Web administration console. He works on
the JavaScript view engine, SpiderMonkey and MochiWeb integration in
addition to an external Python client.</p>
-<p><a href="http://jchris.mfdz.com">J. Chris Anderson</a>, <a href="mailto:jchris@apache.org">jchris@apache.org</a></p>
+<p><a href="http://jchris.mfdz.com">J. Chris Anderson</a>, <a href="mailto:jchris@apache.org">jchris@apache.org</a></p>
<p>Upgraded the Erlang JSON term format. Integrates community patches,
particularly related to the HTTP API and the MapReduce system. Gives talks and
presentations about CouchDB, with an eye toward recruiting more developers.</p>
-<p><a href="http://www.davispj.com/">Paul J. Davis</a>, <a href="mailto:davisp@apache.org">davisp@apache.org</a></p>
+<p><a href="http://www.davispj.com/">Paul J. Davis</a>, <a href="mailto:davisp@apache.org">davisp@apache.org</a></p>
<p>Developed features for the HTTP API as well as helped with recent upgrades
to the MapReduce system. Spends time tracking down various bugs reported in
JIRA.</p>
-<p>Adam Kocoloski, <a href="mailto:kocolosk@apache.org">kocolosk@apache.org</a></p>
+<p>Adam Kocoloski, <a href="mailto:kocolosk@apache.org">kocolosk@apache.org</a></p>
<p>Maintains and extends the replicator. Hacks on various other parts of the
core database.</p>
-<p>Mark Hammond, <a href="mailto:mhammond@apache.org">mhammond@apache.org</a></p>
+<p>Mark Hammond, <a href="mailto:mhammond@apache.org">mhammond@apache.org</a></p>
<p>Windows support.</p>
-<p><a href="http://www.jasondavies.com/">Jason Davies</a>, <a href="mailto:jasondavies@apache.org">jasondavies@apache.org</a></p>
+<p><a href="http://www.jasondavies.com/">Jason Davies</a>, <a href="mailto:jasondavies@apache.org">jasondavies@apache.org</a></p>
<p>Developed various authentication features including cookie-based
authentication and OAuth support.</p>
-<p><a href="http://benoitc.im">Benoît Chesneau</a>, <a href="mailto:benoitc@apache.org">benoitc@apache.org</a></p>
+<p><a href="http://benoitc.im">Benoît Chesneau</a>, <a href="mailto:benoitc@apache.org">benoitc@apache.org</a></p>
<p>Developed the URL rewriter and proxy authentication handlers and provides some
patches. He also maintains the couchapp script and some other tools and
libraries related to CouchDB.</p>
-<p><a href="http://fdmanana.wordpress.com">Filipe Manana</a>, <a href="mailto:fdmanana@apache.org">fdmanana@apache.org</a></p>
+<p><a href="http://fdmanana.wordpress.com">Filipe Manana</a>, <a href="mailto:fdmanana@apache.org">fdmanana@apache.org</a></p>
<p>Contributes mostly to the replicator, some parts of the core database and
the security features.</p>
-<p>Robert Newson, <a href="mailto:rnewson@apache.org">rnewson@apache.org</a></p>
+<p>Robert Newson, <a href="mailto:rnewson@apache.org">rnewson@apache.org</a></p>
<p>Contributes bug fixes and small features.</p>
<div id="clear"></div></div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/community/index.html
----------------------------------------------------------------------
diff --git a/community/index.html b/community/index.html
index ef762a3..3284535 100644
--- a/community/index.html
+++ b/community/index.html
@@ -67,6 +67,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/community/issues.html
----------------------------------------------------------------------
diff --git a/community/issues.html b/community/issues.html
index e24fb03..da09959 100644
--- a/community/issues.html
+++ b/community/issues.html
@@ -69,6 +69,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/community/lists.html
----------------------------------------------------------------------
diff --git a/community/lists.html b/community/lists.html
index 62593b1..8dc661b 100644
--- a/community/lists.html
+++ b/community/lists.html
@@ -69,6 +69,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
@@ -90,11 +94,11 @@ discussion of topics related to CouchDB.</p>
<ul>
<li>To <strong>subscribe</strong>, send an email to
-<a href="mailto:user-subscribe@couchdb.apache.org">user-subscribe@couchdb.apache.org</a>.</li>
+<a href="mailto:user-subscribe@couchdb.apache.org">user-subscribe@couchdb.apache.org</a>.</li>
<li>To <strong>unsubscribe</strong> send empty email to
-<a href="mailto:user-unsubscribe@couchdb.apache.org">user-unsubscribe@couchdb.apache.org</a></li>
+<a href="mailto:user-unsubscribe@couchdb.apache.org">user-unsubscribe@couchdb.apache.org</a></li>
<li>Finally, to post a message to the list use the address
-<a href="mailto:user@couchdb.apache.org">user@couchdb.apache.org</a></li>
+<a href="mailto:user@couchdb.apache.org">user@couchdb.apache.org</a></li>
</ul>
<p>The archives for this list can also be <a href="http://mail-archives.apache.org/mod_mbox/couchdb-user/">browsed online</a>.</p>
@@ -109,11 +113,11 @@ participate if they are interested following development.</p>
<ul>
<li>To <strong>subscribe</strong>, send an email to
-<a href="mailto:dev-subscribe@couchdb.apache.org">dev-subscribe@couchdb.apache.org</a>.</li>
+<a href="mailto:dev-subscribe@couchdb.apache.org">dev-subscribe@couchdb.apache.org</a>.</li>
<li>To <strong>unsubscribe</strong> send empty email to
-<a href="mailto:dev-unsubscribe@couchdb.apache.org">dev-unsubscribe@couchdb.apache.org</a></li>
+<a href="mailto:dev-unsubscribe@couchdb.apache.org">dev-unsubscribe@couchdb.apache.org</a></li>
<li>Finally, to post a message to the list use the address
-<a href="mailto:dev@couchdb.apache.org">dev@couchdb.apache.org</a></li>
+<a href="mailto:dev@couchdb.apache.org">dev@couchdb.apache.org</a></li>
</ul>
<p>The archives for this list can also be <a href="http://mail-archives.apache.org/mod_mbox/couchdb-dev/">browsed online</a>.</p>
@@ -126,9 +130,9 @@ to see and review changes made by others.</p>
<ul>
<li>To <strong>subscribe</strong>, send an email to
-<a href="mailto:commits-subscribe@couchdb.apache.org">commits-subscribe@couchdb.apache.org</a>.</li>
+<a href="mailto:commits-subscribe@couchdb.apache.org">commits-subscribe@couchdb.apache.org</a>.</li>
<li>To <strong>unsubscribe</strong> send empty email to
-<a href="mailto:commits-unsubscribe@couchdb.apache.org">commits-unsubscribe@couchdb.apache.org</a></li>
+<a href="mailto:commits-unsubscribe@couchdb.apache.org">commits-unsubscribe@couchdb.apache.org</a></li>
</ul>
<p>The archives for this list can also be <a href="http://mail-archives.apache.org/mod_mbox/couchdb-commits/">browsed online</a>.</p>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/docs/books.html
----------------------------------------------------------------------
diff --git a/docs/books.html b/docs/books.html
index c1d86ad..b4fddce 100644
--- a/docs/books.html
+++ b/docs/books.html
@@ -69,6 +69,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/docs/index.html
----------------------------------------------------------------------
diff --git a/docs/index.html b/docs/index.html
index d46b333..58a36f6 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -67,6 +67,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/docs/intro.html
----------------------------------------------------------------------
diff --git a/docs/intro.html b/docs/intro.html
index 7236de7..af78762 100644
--- a/docs/intro.html
+++ b/docs/intro.html
@@ -69,6 +69,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/docs/overview.html
----------------------------------------------------------------------
diff --git a/docs/overview.html b/docs/overview.html
index 6522263..7e4fe3d 100644
--- a/docs/overview.html
+++ b/docs/overview.html
@@ -69,6 +69,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="../notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="../notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="../security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/downloads.html
----------------------------------------------------------------------
diff --git a/downloads.html b/downloads.html
index ba02490..b0ac07a 100644
--- a/downloads.html
+++ b/downloads.html
@@ -67,6 +67,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="security.html"><span>Security</span></a></li>
</ul>
</div>
@@ -78,23 +82,12 @@ limitations under the License.
<p><div style="border:5px dashed #F00;padding:1em"></p>
-<p><strong>CAUTION</strong> The 1.0.0 release has a data-loss bug in its default configuration.
-Please stand by and wait for the 1.0.1 release.</p>
-
-<p>If you <em>are</em> running CouchDB 1.0.0 in production, here are the steps to
-reconfigure CouchDB to avoid the bug.</p>
-
-<p><em>It is important that you do not stop or restart the server.</em></p>
+<p><strong>CAUTION</strong></p>
-<pre><code>curl -X PUT http://127.0.0.1:5984/_config/couchdb/delayed_commits -d'"false"'
-</code></pre>
-
-<p>This disables <em>delayed commits</em>, the feature that includes the bug.</p>
+<p>The 1.0.0 release has a data-loss bug in its default configuration.
+Please wait for the 1.0.1 release.</p>
-<p>Then, for each of your databases, run:</p>
-
-<pre><code>curl -X POST http://127.0.0.1:5984/database_name/_ensure_full_commit
-</code></pre>
+<p><a href="notice/1.0.1.html">If you are running version 1.0.0, please read this notice</a>.</p>
<p></div></p>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/downloads.txt
----------------------------------------------------------------------
diff --git a/downloads.txt b/downloads.txt
index 9f90fce..1a49ac8 100644
--- a/downloads.txt
+++ b/downloads.txt
@@ -12,21 +12,12 @@ Current Releases
<div style="border:5px dashed #F00;padding:1em">
-**CAUTION** The 1.0.0 release has a data-loss bug in its default configuration.
-Please stand by and wait for the 1.0.1 release.
+**CAUTION**
-If you *are* running CouchDB 1.0.0 in production, here are the steps to
-reconfigure CouchDB to avoid the bug.
+The 1.0.0 release has a data-loss bug in its default configuration.
+Please wait for the 1.0.1 release.
-*It is important that you do not stop or restart the server.*
-
- curl -X PUT http://127.0.0.1:5984/_config/couchdb/delayed_commits -d'"false"'
-
-This disables *delayed commits*, the feature that includes the bug.
-
-Then, for each of your databases, run:
-
- curl -X POST http://127.0.0.1:5984/database_name/_ensure_full_commit
+[If you are running version 1.0.0, please read this notice](notice/1.0.1.html).
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/index.html
----------------------------------------------------------------------
diff --git a/index.html b/index.html
index 986cadb..f37b7a9 100644
--- a/index.html
+++ b/index.html
@@ -65,6 +65,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/notice/1.0.1.html
----------------------------------------------------------------------
diff --git a/notice/1.0.1.html b/notice/1.0.1.html
new file mode 100644
index 0000000..fb5574d
--- /dev/null
+++ b/notice/1.0.1.html
@@ -0,0 +1,233 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+Copyright 2008 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<html lang="en">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+ <title>Apache CouchDB: Notice for 1.0.1</title>
+ <meta name="description" content="Apache,CouchDB is a distributed, fault-tolerant and schema-free
+ document-oriented database accessible via a RESTful HTTP/JSON API.">
+ <meta name="keywords" content="CouchDB,database,document,REST,HTTP,JSON,Javascript">
+ <link rel="icon" type="img/x-icon" href="../favicon.ico">
+ <link rel="shortcut icon" type="img/x-icon" href="../favicon.ico">
+ <link rel="stylesheet" type="text/css" href="../style/layout.css">
+ <link rel="stylesheet" type="text/css" href="../style/print.css" media="print">
+ </head>
+ <body>
+ <div id="header"><div class="wrap">
+ <a class="couchdb" href="../index.html">
+ <object data="../img/couchdb-logo.svg" width="400" height="110" type="image/svg+xml">
+ <img src="../img/couchdb-logo.png" width="400" height="110" alt="CouchDB - Relax">
+ </object>
+ </a>
+ <h1>Apache CouchDB. Relax.</h1>
+ </div></div>
+ <div id="breadcrumbs"><ul>
+<li><a href="../index.html">Home</a></li>
+<li>»</li>
+<li><a href="index.html">Notices</a></li>
+<li>»</li>
+<li class="active"><a href="1.0.1.html">Notice for 1.0.1</a></li>
+</ul>
+</div>
+ <div id="main"><div class="wrap">
+ <div id="nav"><ul>
+<li><a class="" href="../index.html"><span>Home</span></a></li>
+<li><a class="external" href="http://www.google.com/coop/cse?cx=006426053638666134111:bfy4xffxeqc"><span>Search</span></a></li>
+<li><a class="" href="../downloads.html"><span>Downloads</span></a></li>
+<li><a class="" href="../screenshots.html"><span>Screenshots</span></a></li>
+<li><a class="external" href="http://www.apache.org/licenses/LICENSE-2.0.html"><span>License</span></a></li>
+<li><a class="external" href="https://issues.apache.org/jira/browse/COUCHDB?report=com.atlassian.jira.plugin.system.project:roadmap-panel"><span>Road Map</span></a></li>
+<li><a class="" href="../docs/index.html"><span>Documentation</span></a><ul>
+<li><a class="" href="../docs/intro.html"><span>Introduction</span></a></li>
+<li><a class="" href="../docs/overview.html"><span>Overview</span></a></li>
+<li><a class="external" href="http://wiki.apache.org/couchdb/"><span>Wiki</span></a></li>
+<li><a class="" href="../docs/books.html"><span>Books</span></a></li>
+<li><a class="external" href="http://www.apache.org/foundation/thanks.html"><span>Thanks</span></a></li>
+<li><a class="external" href="http://www.apache.org/foundation/sponsorship.html"><span>Become a Sponsor</span></a></li>
+</ul>
+</li>
+<li><a class="" href="../community/index.html"><span>Get Involved</span></a><ul>
+<li><a class="" href="../community/lists.html"><span>Mailing Lists</span></a></li>
+<li><a class="" href="../community/issues.html"><span>Issue Tracking</span></a></li>
+<li><a class="" href="../community/code.html"><span>Source Code</span></a></li>
+<li><a class="" href="../community/committers.html"><span>Committers</span></a></li>
+<li><a class="external" href="http://wiki.apache.org/couchdb/Coding_Standards"><span>Coding Standards</span></a></li>
+<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
+</ul>
+</li>
+<li><a class="" href="index.html"><span>Notices</span></a><ul>
+<li><a class="active" href="1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
+<li><a class="" href="../security.html"><span>Security</span></a></li>
+</ul>
+</div>
+ <div id="content"><h1>Notice for 1.0.1</h1>
+
+<h2>Warning</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>This bug does not affect earlier releases of CouchDB.</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. 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>
+
+<h2>The Remedy</h2>
+
+<p>For current users, these instructions will ensure your data is safe. First: <strong>do not restart your CouchDB!</strong> The hot fix involves changing configuration on the running server, so have your admin credentials handy (if your CouchDB is in Admin Party mode with no admins defined, you won’t need admin credentials). (If you do not have admin credentials, but you can restart the server, you can still prevent data loss. Read on.)</p>
+
+<h3>If you have admin credentials (or if your CouchDB is in Admin Party mode)</h3>
+
+<p>Visit the Futon admin console at <a href="http://yourserver:5984/_utils/">http://yourserver:5984/_utils/</a>, and click “Login” in the lower right hand corner. Login as an administrator, and visit the “Configuration” page linked in the sidebar: <a href="http://yourserver:5984/_utils/config.html">http://yourserver:5984/_utils/config.html</a></p>
+
+<p>Now that you are in the configuration page, set <code>delayed_commits</code> (in the <code>couchdb</code> section) to <code>false</code>. You can do this by clicking on the word <code>true</code>, and replacing it with false, and hitting enter.</p>
+
+<p>The next time you write a document to each database, it will commit the header to disk, and your data will be secure. For safety, please continue with the next set of instructions.</p>
+
+<h3>For everyone</h3>
+
+<p>To ensure that each database is committed, you can use the <code>_ensure_full_commit</code> command. There are a couple of ways to do this. Here is a simple HTML file that you can upload to your CouchDB using Futon. When you visit it, it will make sure your data is all safely committed. If you prefer a shell script, skip below this file.</p>
+
+<p>Save this HTML to a file on your machine called <code>commit_all.html</code></p>
+
+<pre><code><!DOCTYPE html>
+<html>
+ <head><title>Commit All Databases</title></head>
+ <body>
+ <h1>Commit All Databases</h1>
+ <p>This script will trigger <tt>_ensure_full_commit</tt> on all databases.</p>
+ <ul id="databases"></ul>
+ </body>
+ <script src="/_utils/script/jquery.js"></script>
+ <script src="/_utils/script/jquery.couch.js"></script>
+ <script>
+ $.couch.allDbs({
+ success : function(dbs) {
+ dbs.forEach(function(db) {
+ $.ajax({
+ type: "POST", url: "/" + encodeURIComponent(db) + "/_ensure_full_commit",
+ contentType: "application/json", dataType: "json",
+ complete : function(r) {
+ if (r.status == 201) {
+ $("#databases").append('<li>committed: '+db+'</li>');
+ } else {
+ $("#databases").append('<li style="color:red;">error: '+db+'</li>');
+ }
+ }
+ });
+ });
+ }
+ });
+ </script>
+</html>
+</code></pre>
+
+<p>Now browse to your CouchDB’s Futon at <a href="http://localhost:5984/_utils/">http://localhost:5984/_utils/</a> and create a database. Now visit that database, and create a document, and save it. Now click the button labeled “Upload Attachment” and choose the <code>commit_all.html</code> file you just created, and upload it. A link to that HTML file will appear in Futon.</p>
+
+<p>Now click the link in Futon for <code>commit_all.html</code>, and it will run <code>_ensure_full_commit</code> on all of your databases.</p>
+
+<p>If you prefer a shell script, <a href="http://wiki.couchone.com/page/ensure-full_commit-sh">this will also commit all your databases.</a></p>
+
+<p>At this point your data is safe.</p>
+
+<h3>If you don’t have admin credentials</h3>
+
+<p><strong>Warning:</strong> make sure you followed the instructions in the above section “For everyone” before you do the rest of these steps. If you were able to log into CouchDB as an administrator (and complete the first section, before “For Everyone”) than you can skip this section.</p>
+
+<p>In this step we will configure your CouchDB so that future updates will be durable.</p>
+
+<p>Did you run the above HTML script? Do that now, or the next action may destroy data.</p>
+
+<p>Now, find CouchDB’s configuration file. It will be called <code>local.ini</code> and it is probably in a locations like: <code>/usr/local/etc/couchdb/local.ini</code></p>
+
+<p>Open the file, and add the following lines to it:</p>
+
+<pre><code>[couchdb]
+delayed_commits = false
+</code></pre>
+
+<p>Now, restart your CouchDB. This will be different on different operating systems. If you have your CouchDB configured as a system service, restarting the computer will do the trick, but if you don’t want to do that, you can probably find the pid of CouchDB, by running <code>ps ax | grep couchdb</code>. Once you have the pid, you can kill CouchDB by running <code>kill <pid></code>. If you are a fan of magic, you can do all that in one ninja move by running:</p>
+
+<pre><code> kill `ps ax | grep couchdb | head -n1 | awk '{print $1}'`
+</code></pre>
+
+<p>Note: you might need to sudo.</p>
+
+<p>Once CouchDB is killed, the system should bring it back up. When it boots, it will load the config for <code>delayed_commits = false</code> so updates from that point forward will be durable.</p>
+
+<h2>The Bug</h2>
+
+<p>Now that we have you fixed up, you might enjoy a look at the technicalities of what got broken in CouchDB.</p>
+
+<p>A commit is what causes writes to become durably flushed to storage. It is an expensive operation. During a commit, recent writes are flushed to disk and a new database header is written. Finally, the new header is also flushed to disk. At the operating system level this involves multiple fsync() calls to ensure data has been fully written.</p>
+
+<p>Delayed commits are a feature of CouchDB that allows it to achieve better write performance for some workloads while sacrificing a small amount of durability. The setting causes CouchDB to wait up to a full second before committing new data after an update. If the server crashes before the header is written then any writes since the last commit are lost. The choice of delayed commits as a default has been discussed many times and the consensus was that they should remain on for the 1.0 release.</p>
+
+<p>For each open database in CouchDB there is an erlang process referred to as the update process, the source for which is in a file called <code>couch_db_updater.erl</code>. All writes to a given database pass through the corresponding update process. This process is in charge of preparing, writing and committing batches of updates. In order to provide delayed commits, the update process sets a timer for one second in the future. When the timer expires a commit message is sent back to the updater. A reference to this timer is kept in the updater state. This reference prevents the updater from scheduling excessive commit messages when one is already pending.</p>
+
+<p>In the updater code that shipped with 1.0 a delayed commit message that arrived when there were no pending writes never cleared the timer reference. As a result, the updater state erroneously indicated that there was a future commit scheduled. Once in this bad state the updater would never schedule another commit. In practice, this problem occurred when a write conflict was followed by a period of inactivity. The conflicting write triggered the delayed commit, but when the commit message arrived no new data needed to be written and the timer reference was not cleared. This scenario is thankfully unlikely to occur in a busy database.</p>
+
+<h2>Mixups and Fixes</h2>
+
+<p>One can never say exactly what lead to a particular bug. In this case, there were some contributing factors.</p>
+
+<h3>Release procedure</h3>
+
+<p>In the run-up to 1.0, there was some confusion about which branch would ultimately become 1.0. Originally we’d discussed branching 1.0 from the 0.11.x line, as 0.11 was a feature freeze release, so that we could concentrate on bugs and performance for 1.0. However, as we approached 1.0’s release, there was very little work in trunk that involved new features. And the few features added to trunk were really just refinements of existing functionality, to make it more user friendly, etc.</p>
+
+<p>So in the final weeks before 1.0’s release, we decided to cut it from trunk (as opposed to from the 0.11.x branch) as that would make for more straightforward code management in the future. It has also been our release policy since the early days of the project.</p>
+
+<p>As a result the commit that introduced the bug went into trunk when 0.11.x was still designated to become the 1.0 release with the intention to have it prove its stability before a future 1.1 release. After we decided to cut 1.0 from trunk, this commit didn’t get the necessary review to stay in the 1.0 release branch.</p>
+
+<p>The fix here is that we are now crystal clear that future releases will always be cut from trunk. So if people are committing stuff that they feel is not baked enough for trunk, those commits will be more likely done in a feature branch. Keeping clear about this is one way we can avoid similar issues in the future.</p>
+
+<h3>Code review</h3>
+
+<p>In the run up to 1.0, there were mailing list messages about which commits were trivial, and which needed review. In the case of the commits that weren’t trivial, the original committer was the one who said he thought they were fine. In the future, for any commits to the deepest parts of the storage engine, we will be careful to have review from multiple parties. Many eyes make bugs shallow, but for code like the core CouchDB storage engine, there aren’t a lot of folks who are ready to review and understand a particular patch.</p>
+
+<h3>Testing</h3>
+
+<p>CouchDB currently has a suite of unit and integration tests, which guide development and provide the first line of documentation. We also have a few independent benchmark suites, which we can use to track performance improvements and regressions.</p>
+
+<p>What we don’t have is a set of correctness stress tests. In this case, a fuzzing test, that applies a random set of operations to a constrained keyspace, while tracking the expected database state, and then restarting the server to make sure the state is as expected, would have caught the error.</p>
+
+<p>We could learn a lot from the <a href="http://www.sqlite.org/testing.html">SQLite testing methodology</a>. Expect to see more stress and correctness tests in CouchDB’s future.</p>
+<div id="clear"></div></div>
+ </div></div>
+ <div id="footer">
+ <p class="copyright">Copyright © 2008,2009 <a href="http://www.apache.org/">The Apache Software Foundation</a></p>
+ </div>
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-658988-6']);
+ _gaq.push(['_trackPageview']);
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+ </script>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/notice/1.0.1.txt
----------------------------------------------------------------------
diff --git a/notice/1.0.1.txt b/notice/1.0.1.txt
new file mode 100644
index 0000000..c30785f
--- /dev/null
+++ b/notice/1.0.1.txt
@@ -0,0 +1,138 @@
+Title: Notice for 1.0.1
+Sort-Index: 061
+
+# %(title)s
+
+## Warning
+
+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.
+
+This bug does not affect earlier releases of CouchDB.
+
+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. 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.
+
+## The Remedy
+
+For current users, these instructions will ensure your data is safe. First: **do not restart your CouchDB!** The hot fix involves changing configuration on the running server, so have your admin credentials handy (if your CouchDB is in Admin Party mode with no admins defined, you won't need admin credentials). (If you do not have admin credentials, but you can restart the server, you can still prevent data loss. Read on.)
+
+### If you have admin credentials (or if your CouchDB is in Admin Party mode)
+
+Visit the Futon admin console at <http://yourserver:5984/_utils/>, and click "Login" in the lower right hand corner. Login as an administrator, and visit the "Configuration" page linked in the sidebar: <http://yourserver:5984/_utils/config.html>
+
+Now that you are in the configuration page, set `delayed_commits` (in the `couchdb` section) to `false`. You can do this by clicking on the word `true`, and replacing it with false, and hitting enter.
+
+The next time you write a document to each database, it will commit the header to disk, and your data will be secure. For safety, please continue with the next set of instructions.
+
+### For everyone
+
+To ensure that each database is committed, you can use the `_ensure_full_commit` command. There are a couple of ways to do this. Here is a simple HTML file that you can upload to your CouchDB using Futon. When you visit it, it will make sure your data is all safely committed. If you prefer a shell script, skip below this file.
+
+Save this HTML to a file on your machine called `commit_all.html`
+
+ <!DOCTYPE html>
+ <html>
+ <head><title>Commit All Databases</title></head>
+ <body>
+ <h1>Commit All Databases</h1>
+ <p>This script will trigger <tt>_ensure_full_commit</tt> on all databases.</p>
+ <ul id="databases"></ul>
+ </body>
+ <script src="/_utils/script/jquery.js"></script>
+ <script src="/_utils/script/jquery.couch.js"></script>
+ <script>
+ $.couch.allDbs({
+ success : function(dbs) {
+ dbs.forEach(function(db) {
+ $.ajax({
+ type: "POST", url: "/" + encodeURIComponent(db) + "/_ensure_full_commit",
+ contentType: "application/json", dataType: "json",
+ complete : function(r) {
+ if (r.status == 201) {
+ $("#databases").append('<li>committed: '+db+'</li>');
+ } else {
+ $("#databases").append('<li style="color:red;">error: '+db+'</li>');
+ }
+ }
+ });
+ });
+ }
+ });
+ </script>
+ </html>
+
+Now browse to your CouchDB's Futon at <http://localhost:5984/_utils/> and create a database. Now visit that database, and create a document, and save it. Now click the button labeled "Upload Attachment" and choose the `commit_all.html` file you just created, and upload it. A link to that HTML file will appear in Futon.
+
+Now click the link in Futon for `commit_all.html`, and it will run `_ensure_full_commit` on all of your databases.
+
+If you prefer a shell script, [this will also commit all your databases.](http://wiki.couchone.com/page/ensure-full_commit-sh)
+
+At this point your data is safe.
+
+### If you don't have admin credentials
+
+**Warning:** make sure you followed the instructions in the above section "For everyone" before you do the rest of these steps. If you were able to log into CouchDB as an administrator (and complete the first section, before "For Everyone") than you can skip this section.
+
+In this step we will configure your CouchDB so that future updates will be durable.
+
+Did you run the above HTML script? Do that now, or the next action may destroy data.
+
+Now, find CouchDB's configuration file. It will be called `local.ini` and it is probably in a locations like: `/usr/local/etc/couchdb/local.ini`
+
+Open the file, and add the following lines to it:
+
+ [couchdb]
+ delayed_commits = false
+
+Now, restart your CouchDB. This will be different on different operating systems. If you have your CouchDB configured as a system service, restarting the computer will do the trick, but if you don't want to do that, you can probably find the pid of CouchDB, by running `ps ax | grep couchdb`. Once you have the pid, you can kill CouchDB by running `kill <pid>`. If you are a fan of magic, you can do all that in one ninja move by running:
+
+ kill `ps ax | grep couchdb | head -n1 | awk '{print $1}'`
+
+Note: you might need to sudo.
+
+Once CouchDB is killed, the system should bring it back up. When it boots, it will load the config for `delayed_commits = false` so updates from that point forward will be durable.
+
+## The Bug
+
+Now that we have you fixed up, you might enjoy a look at the technicalities of what got broken in CouchDB.
+
+A commit is what causes writes to become durably flushed to storage. It is an expensive operation. During a commit, recent writes are flushed to disk and a new database header is written. Finally, the new header is also flushed to disk. At the operating system level this involves multiple fsync() calls to ensure data has been fully written.
+
+Delayed commits are a feature of CouchDB that allows it to achieve better write performance for some workloads while sacrificing a small amount of durability. The setting causes CouchDB to wait up to a full second before committing new data after an update. If the server crashes before the header is written then any writes since the last commit are lost. The choice of delayed commits as a default has been discussed many times and the consensus was that they should remain on for the 1.0 release.
+
+For each open database in CouchDB there is an erlang process referred to as the update process, the source for which is in a file called `couch_db_updater.erl`. All writes to a given database pass through the corresponding update process. This process is in charge of preparing, writing and committing batches of updates. In order to provide delayed commits, the update process sets a timer for one second in the future. When the timer expires a commit message is sent back to the updater. A reference to this timer is kept in the updater state. This reference prevents the updater from scheduling excessive commit messages when one is already pending.
+
+In the updater code that shipped with 1.0 a delayed commit message that arrived when there were no pending writes never cleared the timer reference. As a result, the updater state erroneously indicated that there was a future commit scheduled. Once in this bad state the updater would never schedule another commit. In practice, this problem occurred when a write conflict was followed by a period of inactivity. The conflicting write triggered the delayed commit, but when the commit message arrived no new data needed to be written and the timer reference was not cleared. This scenario is thankfully unlikely to occur in a busy database.
+
+## Mixups and Fixes
+
+One can never say exactly what lead to a particular bug. In this case, there were some contributing factors.
+
+### Release procedure
+
+In the run-up to 1.0, there was some confusion about which branch would ultimately become 1.0. Originally we'd discussed branching 1.0 from the 0.11.x line, as 0.11 was a feature freeze release, so that we could concentrate on bugs and performance for 1.0. However, as we approached 1.0's release, there was very little work in trunk that involved new features. And the few features added to trunk were really just refinements of existing functionality, to make it more user friendly, etc.
+
+So in the final weeks before 1.0's release, we decided to cut it from trunk (as opposed to from the 0.11.x branch) as that would make for more straightforward code management in the future. It has also been our release policy since the early days of the project.
+
+As a result the commit that introduced the bug went into trunk when 0.11.x was still designated to become the 1.0 release with the intention to have it prove its stability before a future 1.1 release. After we decided to cut 1.0 from trunk, this commit didn't get the necessary review to stay in the 1.0 release branch.
+
+The fix here is that we are now crystal clear that future releases will always be cut from trunk. So if people are committing stuff that they feel is not baked enough for trunk, those commits will be more likely done in a feature branch. Keeping clear about this is one way we can avoid similar issues in the future.
+
+### Code review
+
+In the run up to 1.0, there were mailing list messages about which commits were trivial, and which needed review. In the case of the commits that weren't trivial, the original committer was the one who said he thought they were fine. In the future, for any commits to the deepest parts of the storage engine, we will be careful to have review from multiple parties. Many eyes make bugs shallow, but for code like the core CouchDB storage engine, there aren't a lot of folks who are ready to review and understand a particular patch.
+
+### Testing
+
+CouchDB currently has a suite of unit and integration tests, which guide development and provide the first line of documentation. We also have a few independent benchmark suites, which we can use to track performance improvements and regressions.
+
+What we don't have is a set of correctness stress tests. In this case, a fuzzing test, that applies a random set of operations to a constrained keyspace, while tracking the expected database state, and then restarting the server to make sure the state is as expected, would have caught the error.
+
+We could learn a lot from the [SQLite testing methodology](http://www.sqlite.org/testing.html). Expect to see more stress and correctness tests in CouchDB's future.
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/notice/index.html
----------------------------------------------------------------------
diff --git a/notice/index.html b/notice/index.html
new file mode 100644
index 0000000..8c3617a
--- /dev/null
+++ b/notice/index.html
@@ -0,0 +1,98 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
+ "http://www.w3.org/TR/html4/strict.dtd">
+<!--
+Copyright 2008 The Apache Software Foundation
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+-->
+<html lang="en">
+ <head>
+ <meta http-equiv="Content-Type" content="text/html;charset=utf-8">
+ <title>Apache CouchDB: Notices</title>
+ <meta name="description" content="Apache,CouchDB is a distributed, fault-tolerant and schema-free
+ document-oriented database accessible via a RESTful HTTP/JSON API.">
+ <meta name="keywords" content="CouchDB,database,document,REST,HTTP,JSON,Javascript">
+ <link rel="icon" type="img/x-icon" href="../favicon.ico">
+ <link rel="shortcut icon" type="img/x-icon" href="../favicon.ico">
+ <link rel="stylesheet" type="text/css" href="../style/layout.css">
+ <link rel="stylesheet" type="text/css" href="../style/print.css" media="print">
+ </head>
+ <body>
+ <div id="header"><div class="wrap">
+ <a class="couchdb" href="../index.html">
+ <object data="../img/couchdb-logo.svg" width="400" height="110" type="image/svg+xml">
+ <img src="../img/couchdb-logo.png" width="400" height="110" alt="CouchDB - Relax">
+ </object>
+ </a>
+ <h1>Apache CouchDB. Relax.</h1>
+ </div></div>
+ <div id="breadcrumbs"><ul>
+<li><a href="../index.html">Home</a></li>
+<li>»</li>
+<li class="active"><a href="index.html">Notices</a></li>
+</ul>
+</div>
+ <div id="main"><div class="wrap">
+ <div id="nav"><ul>
+<li><a class="" href="../index.html"><span>Home</span></a></li>
+<li><a class="external" href="http://www.google.com/coop/cse?cx=006426053638666134111:bfy4xffxeqc"><span>Search</span></a></li>
+<li><a class="" href="../downloads.html"><span>Downloads</span></a></li>
+<li><a class="" href="../screenshots.html"><span>Screenshots</span></a></li>
+<li><a class="external" href="http://www.apache.org/licenses/LICENSE-2.0.html"><span>License</span></a></li>
+<li><a class="external" href="https://issues.apache.org/jira/browse/COUCHDB?report=com.atlassian.jira.plugin.system.project:roadmap-panel"><span>Road Map</span></a></li>
+<li><a class="" href="../docs/index.html"><span>Documentation</span></a><ul>
+<li><a class="" href="../docs/intro.html"><span>Introduction</span></a></li>
+<li><a class="" href="../docs/overview.html"><span>Overview</span></a></li>
+<li><a class="external" href="http://wiki.apache.org/couchdb/"><span>Wiki</span></a></li>
+<li><a class="" href="../docs/books.html"><span>Books</span></a></li>
+<li><a class="external" href="http://www.apache.org/foundation/thanks.html"><span>Thanks</span></a></li>
+<li><a class="external" href="http://www.apache.org/foundation/sponsorship.html"><span>Become a Sponsor</span></a></li>
+</ul>
+</li>
+<li><a class="" href="../community/index.html"><span>Get Involved</span></a><ul>
+<li><a class="" href="../community/lists.html"><span>Mailing Lists</span></a></li>
+<li><a class="" href="../community/issues.html"><span>Issue Tracking</span></a></li>
+<li><a class="" href="../community/code.html"><span>Source Code</span></a></li>
+<li><a class="" href="../community/committers.html"><span>Committers</span></a></li>
+<li><a class="external" href="http://wiki.apache.org/couchdb/Coding_Standards"><span>Coding Standards</span></a></li>
+<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
+</ul>
+</li>
+<li><a class="active" href="index.html"><span>Notices</span></a><ul>
+<li><a class="" href="1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
+<li><a class="" href="../security.html"><span>Security</span></a></li>
+</ul>
+</div>
+ <div id="content"><h1>Notices</h1>
+
+<ul>
+<li><a href="1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+<div id="clear"></div></div>
+ </div></div>
+ <div id="footer">
+ <p class="copyright">Copyright © 2008,2009 <a href="http://www.apache.org/">The Apache Software Foundation</a></p>
+ </div>
+ <script type="text/javascript">
+ var _gaq = _gaq || [];
+ _gaq.push(['_setAccount', 'UA-658988-6']);
+ _gaq.push(['_trackPageview']);
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
+ })();
+ </script>
+ </body>
+</html>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/notice/index.txt
----------------------------------------------------------------------
diff --git a/notice/index.txt b/notice/index.txt
new file mode 100644
index 0000000..b8e739c
--- /dev/null
+++ b/notice/index.txt
@@ -0,0 +1,8 @@
+Title: Notices
+Sort-Index: 070
+
+
+%(title)s
+=========
+
+%(children)s
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/screenshots.html
----------------------------------------------------------------------
diff --git a/screenshots.html b/screenshots.html
index 83961e7..4b7dc32 100644
--- a/screenshots.html
+++ b/screenshots.html
@@ -67,6 +67,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="" href="security.html"><span>Security</span></a></li>
</ul>
</div>
http://git-wip-us.apache.org/repos/asf/couchdb/blob/a419e8d1/security.html
----------------------------------------------------------------------
diff --git a/security.html b/security.html
index 7b76e24..93d3668 100644
--- a/security.html
+++ b/security.html
@@ -67,6 +67,10 @@ limitations under the License.
<li><a class="external" href="http://planet.couchdb.com/"><span>Planet</span></a></li>
</ul>
</li>
+<li><a class="" href="notice/index.html"><span>Notices</span></a><ul>
+<li><a class="" href="notice/1.0.1.html"><span>Notice for 1.0.1</span></a></li>
+</ul>
+</li>
<li><a class="active" href="security.html"><span>Security</span></a></li>
</ul>
</div>