Skip to content

Commit

Permalink
Merge pull request #99 from mojombo/better-wording-faq
Browse files Browse the repository at this point in the history
Reword scenario of accidental breaking changes
  • Loading branch information
haacked committed Jun 1, 2013
2 parents 7a8bae9 + ff4fb48 commit 62c2005
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion semver.md
Expand Up @@ -194,7 +194,7 @@ modification depends on whether you updated your dependencies in order to fix
a bug or introduce new functionality. I would usually expect additional code
for the latter instance, in which case it's obviously a minor level increment.

### What should I do if the bug that is being fixed returns the code to being compliant with the public API (i.e. the code was incorrectly out of sync with the public API documentation)?
### What if I inadvertently alter the public API in a way that is not compliant with the version number change (i.e. the code incorrectly introduces a major breaking change in a patch release)

Use your best judgment. If you have a huge audience that will be drastically
impacted by changing the behavior back to what the public API intended, then
Expand Down

0 comments on commit 62c2005

Please sign in to comment.