From: Loic Dachary <loic@dachary.org>
To: Joao Eduardo Luis <joao@suse.de>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
"ceph-users@lists.ceph.com" <ceph-users@lists.ceph.com>
Subject: Re: RFC: Deprecating ceph-tool commands
Date: Sat, 09 May 2015 10:57:48 +0200 [thread overview]
Message-ID: <554DCC0C.7040000@dachary.org> (raw)
In-Reply-To: <554D4CD8.6020809@suse.de>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
Hi,
On 09/05/2015 01:55, Joao Eduardo Luis wrote:
> This approach gives a lifespan of roughly 3 releases (at current rate,
> roughly 1.5 years) before being completely dropped. This should give
> enough time to people to realize what has happened and adjust any
> scripts they may have.
That sounds reasonable.
In the python documentation I find it very convenient to have "New in X.Y.Z" next to a given API call or behavior, as well as "Deprectated since". Although release notes https://github.com/ceph/ceph/commit/e3b788a56c640fb19d8aa9464ebf5bc84c97ec6f are useful when upgrading (to answer the question "What API will break ?"), it's not the primary location I'll check when considering using something.
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-05-09 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 23:55 RFC: Deprecating ceph-tool commands Joao Eduardo Luis
[not found] ` <554D4CD8.6020809-l3A5Bk7waGM@public.gmane.org>
2015-05-09 0:28 ` Gregory Farnum
[not found] ` <CAC6JEv9++PqXAkPSykDzN1=7atpTZWuzAZviSY9qWkMis9JStg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-05-09 8:31 ` Joao Eduardo Luis
2015-05-09 8:57 ` Loic Dachary [this message]
[not found] ` <554DCC0C.7040000-cLsNCMjd+0JAfugRpC6u6w@public.gmane.org>
2015-05-09 15:01 ` Joao Eduardo Luis
2015-05-11 10:33 ` [ceph-users] " John Spray
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=554DCC0C.7040000@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=ceph-users@lists.ceph.com \
--cc=joao@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.