On Wed, Jul 4, 2012 at 9:33 AM, Sage Weil <sage@xxxxxxxxxxx> 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... Yep, should probably bump it to .49 then! (Since that's the version it will be part of, and nobody will get confused and try to bump it again before that release.) On Thu, Jul 5, 2012 at 12:26 AM, Wido den Hollander <wido@xxxxxxxxx> wrote: > 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. Well, the problem with bumping it on every Ceph version is that it becomes a lot harder for tools to sync up to a known version of the API. Perhaps we should have divorced it from the Ceph versioning completely, but I don't know if we can still do that in a reasonable way or not. :/ -Greg -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
