Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: error (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: Releasing experimental features (was: Re: [PROPOSAL] Port
 _db_updates from rcouch to master)
From: Filippo Fadda <filippo.fadda@programmazione.it>
In-Reply-To: <B080A760-BAC9-42AE-A4DA-E0C6772C299C@apache.org>
Date: Mon, 22 Jul 2013 13:47:49 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BC7FD9A6-C3A7-4C1E-83D0-86083DAFEFCD@programmazione.it>
References: <7D8897CB-8A85-4A57-9ACA-FB9B3715D351@apache.org>
 <CAJNb-9qAcJ5RQ3akpydDkR6yvR8Bw0L_RdaZUyoqx4Sq=qKm7Q@mail.gmail.com>
 <CAPaJBx7BcAm7T07NNpo18+HqcxEOs=QOE4K-Yq4wJ23sHkw8HA@mail.gmail.com>
 <7A898837-D997-478A-92D7-0C9341BA86B6@apache.org>
 <CAHdjipJWLsO+XCuiYSRJqq2jDHsuA7GW4miMYZucYbK7yBG66g@mail.gmail.com>
 <B080A760-BAC9-42AE-A4DA-E0C6772C299C@apache.org>
To: dev@couchdb.apache.org

Experimental in PHP is used for extensions that are not bundled with =
PHP. Instead deprecated is used to inform the user that a function =
shouldn't be used anymore. In the same way CouchDB could inform that an =
API is deprecated or experimental.

1) X-Couch-Deprecated
2) X-Couch-Experimental

Stable makes no sense at all, and unstable too, because an unstable =
feature should not be included in an official release.

My two cents.

-Filippo


On Jul 22, 2013, at 12:21 PM, Jan Lehnardt wrote:

>=20
> On Jul 22, 2013, at 12:13 , Alexander Shorin <kxepal@gmail.com> wrote:
>=20
>> On Mon, Jul 22, 2013 at 1:48 PM, Jan Lehnardt <jan@apache.org> wrote:
>>> We have talked about deprecating features using HTTP headers like
>>> `X-Couch-Deprecated: true` to denote a deprecation to be included in
>>> releases that happen before the actual removal of a feature. We =
could
>>> make that `X-Couch-API-Stability: [0-5]` instead, if we adopt the =
scale
>>> above (and maybe only optionally show anything >0 to save some bytes
>>> in the general case). And whatever powers that information could be
>>> used to feed into the capabilities we have talked about for the =
welcome
>>> message on `/`.
>>=20
>> X-Couch-API-Stability idea is too complex. Better to have only
>> `X-Couch-Deprecated: true`. Experimental features should be enabled =
in
>> configs so user takes responsibility for any behavior it provides.
>=20
> Fair point, happy to have the 1-5 scale in docs only, if we want to=20
> go that route.
>=20
>> Also, this information is useless in caps. Caps notifies what server
>> able to do, not how good he can.
>=20
> Well, if we have comprehensive encoded info on what state everything
> is in, we will also know what we have, which could be used to form
> the capabilities info.
>=20
> Best
> Jan
> --
>=20
>=20
>=20