Jtapplecalendar: Semantic versioning? 6.0.3 broke scrollToPreviousSegment

Created on 1 Dec 2016 · 5Comments · Source: patchthecode/JTAppleCalendar

Why are breaking changes introduced in patch versions???
Obviously, there were some significant changes in the segmenting code, but this should not be introduced in such a way...

As a reminder, here it is how it is supposed to work:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.

Source

MoridinBG

All 5 comments

Yea i know about semantic versioning.
but honestly.. i forgot about that code change until you just brought it up... ☹️
But don't be too mad k? I'm just one guy with a tonne of code.
Hopefully its not too bad a fix.

patchthecode on 1 Dec 2016

Hey, I am not mad!
Quite the opposite, you are doing an awesome job with this library!
I was just a bit irked when the project stopped building even though I only update patch or minor versions of the pods (:

MoridinBG on 2 Dec 2016

👍1

Ok its cool. But you're right. I'll look more closely next time. Thanks man.
I'll leave this open for a while in case any one else mentions it.

patchthecode on 2 Dec 2016

👍1

Just to save folks some time:

calendarView.scrollToSegment(.previous)

calendarView.scrollToSegment(.next)