Jordan, quick semantic versioning tutorial: If you have 1.0.0 and 1.0.1, you can use either one and you will not run into errors due to API conflicts (i.e. no ClassNotFound or NoSuchMethod type exceptions)
If you have 1.0.0 and 1.1.0, you can replace 1.0.0 with 1.1.0 and you will not have errors due to API conflicts. If you try to swap 1.0.0 in place of something that depends on 1.1.0, however, you *might* have errors due to API conflicts. I.e. you can go forward without errors, but not backwards If you have 1.0.0 and 2.0.0, you will likely have errors due to API conflicts if you replace either one with the other. Hope that helps, if not, feel free to completely ignore me :) --Eric On Tue, Jul 29, 2014 at 5:18 PM, Jordan Zimmerman <[email protected]> wrote: > Though, the api change is backward compatible. Frankly, semantic versioning > confuses me most of the time. > > -JZ > > From: Cameron McKenzie <[email protected]> > Reply: Cameron McKenzie <[email protected]>> > Date: July 29, 2014 at 5:15:49 PM > To: Jordan Zimmerman <[email protected]>> > Cc: [email protected] <[email protected]>> > Subject: Re: Fix for CURATOR-42 > > Ok, thanks. Also, have we decided against doing a 2.6.1? I noticed that this > version is gone and only 2.7.0 is available. > cheers > > > On Wed, Jul 30, 2014 at 8:14 AM, Jordan Zimmerman > <[email protected]> wrote: > Next time just create a PR - I made one. Looks good to me. > > -JZ > > From: Cameron McKenzie <[email protected]> > Reply: [email protected] <[email protected]>>, > [email protected] <[email protected]>> > Date: July 29, 2014 at 5:09:56 PM > To: [email protected] <[email protected]>> > Subject: Fix for CURATOR-42 > > I've just committed a fix for CURATOR-42. Can someone give it a review > please? > cheers > Cam >
