Repository: couchdb-www Updated Branches: refs/heads/api-wait-time 7ff1a95e6 -> 4a234b490 (forced update)
Strengthen requirements on backwards-incompatible API changes Project: http://git-wip-us.apache.org/repos/asf/couchdb-www/repo Commit: http://git-wip-us.apache.org/repos/asf/couchdb-www/commit/4a234b49 Tree: http://git-wip-us.apache.org/repos/asf/couchdb-www/tree/4a234b49 Diff: http://git-wip-us.apache.org/repos/asf/couchdb-www/diff/4a234b49 Branch: refs/heads/api-wait-time Commit: 4a234b4900e9472d157222206ba9ec018a0f0468 Parents: 7a93d54 Author: Joan Touzet <woh...@apache.org> Authored: Thu Feb 8 00:13:28 2018 -0500 Committer: Joan Touzet <woh...@apache.org> Committed: Thu Feb 8 00:22:18 2018 -0500 ---------------------------------------------------------------------- bylaws.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/couchdb-www/blob/4a234b49/bylaws.html ---------------------------------------------------------------------- diff --git a/bylaws.html b/bylaws.html index dde2319..754c534 100644 --- a/bylaws.html +++ b/bylaws.html @@ -286,11 +286,13 @@ <p>For electing a new Chair, the PMC may opt to use <em>Single Transferable Vote</em> (STV) which comes with its own rules. <a href="http://steve.apache.org/";>Apache STeVe</a> was specifically designed to enable this process. -<h3 id="rtc">3.5. RTC and Vetos</h3> +<h3 id="rtc">3.5. Review-Then-Commit, API Changes and Technical Vetos</h3> <p>Typically, CouchDB uses the <a href="http://www.apache.org/foundation/glossary.html#ReviewThenCommit";>Review-Then-Commit</a> (<em>RTC</em>) model of code collaboration. RTC allows work to proceed on separate feature or bugfix branches, and requires at least one other developer to review and approve the changes before they are committed to a release branch. A release branch is any branch that a release might be prepared from, such as <code>master</code>, <code>1.6.x</code>, and so on. Notifications of these changes are sent to <a href="https://mail-archives.apache.org/mod_mbox/couchdb-commits/";>the commits mailing list</a>. It is expected that the rest of the community is regularly reviewing these changes. -<p><strong>Any change made to a release branch is a <em>technical decision</em> of the project. If a committer wants to object to a technical decision, they have the option of casting a -1 vote. We call this a veto.</strong> Vetos can only be made for technical reasons. A -1 vote is not considered a veto in any other context. Vetos should be used sparingly, and only after careful consideration. +<p>Whenever a change is proposed to a release branch or <code>master</code> that removes or changes an existing HTTP API endpoint in a way that breaks backwards compatibility, the proposed change <strong><em>must</em> be announced on the developer mailing list, and a minimum of a <a href="#lazy">lazy consensus</a> decision is required.</strong> Additions of new endpoints, or changes that do not affect backwards compatibility, do not require this notification and process, but announcement to the developer mailing list is still strongly encouraged.</p> + +<p><strong>Any change made to a release branch or to the <code>master</code> branch is a <em>technical decision</em> of the project. If a committer wants to object to a technical decision, they have the option of casting a -1 vote. We call this a veto.</strong> Vetos can only be made for technical reasons. A -1 vote is not considered a veto in any other context. Vetos should be used sparingly, and only after careful consideration. <p>All vetoes must be justified and vetoes without justification are null and void. The validity of the justification can be challenged and the outcome is decided with a vote. If the justification is valid, a veto cannot be overruled and stands until withdrawn by the caster. If you disagree with a veto, you must lobby the person casting the veto to withdraw their veto. If a veto is not withdrawn, the commit must be reverted in a timely manner.
