John Mulligan

> One of the goals listed in the description of this issue is: > > * Aim for 100% test coverage (according to golang native coverage tool) > ... >...

Regarding: `Define a release cycle and release process` A few of us met in a video chat and discussed this. We plan on creating an initial release called "0.2" on...

Heh. I stared working on callback support over the weekend (see https://github.com/phlogistonjohn/go-ceph/commits/jjm-diff-iterate-1). Did you have some code for callbacks too? I agree that we can consider the API "very unstable"...

My thought is to support the oldest of the supported go versions. Whenever we do a release it can then act as a checkpoint if we want to consume newer...

Oh, like a sort of inotify kind of interface in libcephfs? I don't currently know of such a thing, and looking over the list of functions in libcephfs.h I don't...

@ansiwen - any interest in looking into this one?

This bot is happy to oblige.

@nixpanic @ansiwen do you think this is worth keeping open or should we perhaps just remove the perma-skipped test? I realize this may be a sore point in how ceph...

Thanks! CCing @leseb and @thotz as our experts on rgw for scoping. If either of think it's a good fit for go-ceph we'll label this issues appropriately.

Could you link to an example of this API please? Either code or docs would be suitable. Also, I'm not clear what you mean by "multiple incompatible ways". Do you...