Hi Jason
I recently had massive fiasco on my hands when a live site was completely trashed because of an update to Ardent. After two late nights and lots of coffee I vowed never to use "dev-master" in my compser file again, and always code against a specific version of a project
I could use a specific commit id (in this case 1a61b42), but we'd loose out on the advantage that Semantic Versioning (http://semver.org/) give us. The basics are
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.
I'd like to use your code and would appreciate if you'd consider tagging it.
Thank you.
Hi Jason
I recently had massive fiasco on my hands when a live site was completely trashed because of an update to Ardent. After two late nights and lots of coffee I vowed never to use "dev-master" in my compser file again, and always code against a specific version of a project
I could use a specific commit id (in this case 1a61b42), but we'd loose out on the advantage that Semantic Versioning (http://semver.org/) give us. The basics are
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.
I'd like to use your code and would appreciate if you'd consider tagging it.
Thank you.