Versioning
-
If you need adopt a version schema for your projects, you might want to understand how the Ruby Core itself handles versioning.
-
And for information about typical Gem versioning:
-
-
@dan rathbun said:
If you need adopt a version schema for your projects, you might want to understand how the Ruby Core itself handles versioning.
@unknownuser said:
Version Schema
MAJOR: increased when incompatible change which can’t be released in MINOR Reserved for special events MINOR: increased every christmas, may be API incompatible TEENY: security or bug fix which maintains API compatibility May be increased more than 10 (such as 2.1.11), and will be released every 2-3 months. PATCH: number of commits since last MINOR release (will be reset at 0 when releasing MINOR)I didn't see where semver mentions bumping versions at Christmas, special events, or arbitrarily every 2-3 months. Is this versioning or marketing?
Maybe something was mangled in translation to English.
-
-
Ah, so that just means yearly releases. So your encoding bugs might be fixed in 2.2.0 when release in December.
-
It's still unclear what release they are scheduled for. Sometimes these things end up in new releases only - some times they backport the fixes.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register LoginAdvertisement