title: Semantic Versioning when an update breaks backwards compatibilty with a previous minor version
body: <p>If I fork a project on github with version <code>v1.0.0</code> and then add some new functionality. It still remains backwards compatible so if I understand semantic versioning correctly I change the version to <code>v1.1.0</code>. If I now decide I want to change the command line arguments for the new feature, does it become <code>v1.2.0</code>, or <code>v2.0.0</code> since this change would break backwards compatibility introduced in <code>v1.1.0</code>?</p>