On Sat, Jan 25, 2014 at 4:04 PM, Harshavardhana <har...@harshavardhana.net>wrote:
> > "In essence, every time you make a change to the library and > > release it, the C:R:A should change. A new library should start > > with 0:0:0. Each time you change the public interface > > (i.e., your installed header files), you should increment the > > CURRENT number." > > > > So the version which was 3 became 5 when discard API was added and > became 6 > > when zerofill was added. As per the above description, API addition will > > result in a change to the installed header(glfs.h) and hence warrants a > > change in CURRENT number ? Should you have changed the version to 6.0.0 > > instead of 0.0.6 ? > > > > You are in-fact correct here - i didn't know about the API changes with 3, > 5, 6. > I will send out a patch regarding that. Basis on bumping the 'AGE' was > wrong - since > i just assumed public interface didn't change. > Not for this specific change, but may be it's time to add a test case into gluster to test QEMU requirements. The last effort in that direction was made here: http://lists.nongnu.org/archive/html/gluster-devel/2013-02/msg00014.html Regards, Bharata.
_______________________________________________ Gluster-devel mailing list Gluster-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/gluster-devel
