Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

semver? #31

Open
jpdevries opened this issue Mar 15, 2014 · 2 comments
Open

semver? #31

jpdevries opened this issue Mar 15, 2014 · 2 comments

Comments

@jpdevries
Copy link

Just wondering if ace intends follow semver. I noticed the latest patch release, 1.4.3 contains an awesome new auto complete feature. Seems like that should be a minor release (1.5.0) if not major (2.0.0).

Given a version number MAJOR.MINOR.PATCH, increment the:
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.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

@danyaPostfactum
Copy link
Owner

My bad. You are absolutely right. Thanks for noticing. I'll try to follow semver rules henceforth.

@jpdevries
Copy link
Author

I still get completely confused by them, but one rule of thumb is new features equals minor bump—
Sent from Mailbox for iPhone

On Tue, Mar 18, 2014 at 8:50 PM, danyaPostfactum [email protected]
wrote:

My bad. You are absolutely right. Thanks for noticing. I'll try to follow semver rules henceforth.

Reply to this email directly or view it on GitHub:
#31 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants