From: Wido den Hollander <wido@widodh.nl>
To: Sage Weil <sage@inktank.com>
Cc: Gregory Farnum <greg@inktank.com>, ceph-devel@vger.kernel.org
Subject: Re: [PATCH] librados: Bump the version to 0.48
Date: Thu, 05 Jul 2012 09:26:26 +0200 [thread overview]
Message-ID: <4FF541A2.4000003@widodh.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.1207040932090.6931@cobra.newdream.net>
On 07/04/2012 06:33 PM, Sage Weil wrote:
> On Wed, 4 Jul 2012, Gregory Farnum wrote:
>> Hmmm ÿÿ we generally try to modify these versions when the API changes,
>> not on every sprint. It looks to me like Sage added one function in 0.45
>> where we maybe should have bumped it, but that was a long time ago and
>> at this point we should maybe just eat it?
>
> Yeah, I went ahead and applied this to stable (argonaut) since it's as
> good a reference point as any. Moving forward, we should try to sync
> this up with API changes as they happen. Hmm, like that assert
> ObjectOperation that just went into master...
That was my reasoning. I compiled phprados against 0.48 and saw that
librados was reporting 0.44 as version.
That could confuse users and they might think they still have an old
library in place.
Imho the version numbering should be totally different from Ceph if you
only want to bump the version on an API change.
Wido
>
> sage
>
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-07-05 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 13:46 [PATCH] librados: Bump the version to 0.48 Wido den Hollander
2012-07-04 16:29 ` Gregory Farnum
2012-07-04 16:33 ` Sage Weil
2012-07-05 7:26 ` Wido den Hollander [this message]
2012-07-05 22:33 ` Gregory Farnum
2012-07-06 8:52 ` Wido den Hollander
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=4FF541A2.4000003@widodh.nl \
--to=wido@widodh.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=greg@inktank.com \
--cc=sage@inktank.com \
/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.