paulghaddad · February 11, 2015 18:48
diff --git a/gistfile1.txt b/gistfile1.txt
 1. Explain the situations under which you bump the patch / minor / major version number on your software.

 - The Major version number is incremented when API changes will break past versions of the software (1.0.0 -> 2.0.0)
 - The minor version number is incremented when functionality is added that does not break past versions of the software or deprecates API functionality. (1.0.0 -> 1.1.0)
 - The patch version number is incremented after backwards-compatible bug fixes. (1.1.0 -> 1.1.1)

 2. How does that versioning relate to the consumers of your code?

 Semantic Versioning communicates your intentions to your code's users of how your change will affect them. They can, in turn, make flexible dependency decisions. For example, Rails depends on the Sprokets gem. If Sprokets increments its version with a major patch, Rails itself can't depend on the new version of Sprockets working. The Gemfile can then specify the range of versions compatible with Rails.
	1. Explain the situations under which you bump the patch / minor / major version number on your software.

	- The Major version number is incremented when API changes will break past versions of the software (1.0.0 -> 2.0.0)
	- The minor version number is incremented when functionality is added that does not break past versions of the software or deprecates API functionality. (1.0.0 -> 1.1.0)
	- The patch version number is incremented after backwards-compatible bug fixes. (1.1.0 -> 1.1.1)

	2. How does that versioning relate to the consumers of your code?

	Semantic Versioning communicates your intentions to your code's users of how your change will affect them. They can, in turn, make flexible dependency decisions. For example, Rails depends on the Sprokets gem. If Sprokets increments its version with a major patch, Rails itself can't depend on the new version of Sprockets working. The Gemfile can then specify the range of versions compatible with Rails.