-
Notifications
You must be signed in to change notification settings - Fork 24
AgileForOpenSource
John Ament edited this page Feb 28, 2014
·
2 revisions
Basically, this is a high level doc on my process for release, build and testing.
- When a feature works, it ships and ship whenever a feature works.
- Automate all tests. Something doesn't work unless there's a test for it.
- Update the docs. Within a few days of a release, ensure all docs are up to date and match what it really does. Don't document the future.
Versions are based on a three point semantic version. Every release should be considered production ready, with a major version representing concrete workable code, minor versions representing little bits of changes mid release and a minor version change being a bug fix or alpha type code. Changes within alpha releases may change between builds.