dstelow notes…

Archive for January 2010

links for 2010-01-31

leave a comment »

Advertisements

Written by dstelow

January 31, 2010 at 11:01 pm

Posted in 1

links for 2010-01-30

leave a comment »

Written by dstelow

January 30, 2010 at 11:01 pm

Posted in 1

links for 2010-01-27

leave a comment »

Written by dstelow

January 27, 2010 at 11:04 pm

Posted in 1

links for 2010-01-26

leave a comment »

Written by dstelow

January 26, 2010 at 11:03 pm

Posted in 1

links for 2010-01-25

leave a comment »

Written by dstelow

January 25, 2010 at 11:01 pm

Posted in 1

links for 2010-01-20

leave a comment »

Written by dstelow

January 20, 2010 at 11:10 pm

Posted in 1

links for 2010-01-18

leave a comment »

  • As a solution to this problem, I propose a simple set of rules and requirements that dictate how version numbers are assigned and incremented. For this system to work, you first need to declare a public API. This may consist of documentation or be enforced by the code itself. Regardless, it is important that this API be clear and precise. Once you identify your public API, you communicate changes to it with specific increments to your version number. Consider a version format of X.Y.Z (Major.Minor.Patch). Bug fixes not affecting the API increment the patch version, backwards compatible API additions/changes increment the minor version, and backwards incompatible API changes increment the major version.

Written by dstelow

January 18, 2010 at 11:03 pm

Posted in 1