naparuba/shinken — Issue #115: Release checklist for milestone 1.0
Author: xkilian
Created: 2012-01-19 17:51:47+00:00
State: open

Proposed release checklist for review, to make sure all bases are covered. You may already have one somewhere, but I did not see it.

- Announce feature freeze (Nap has already done a pass on all the issues) Each dev should announce on the mailing list perhaps, what he is aiming for in 1.0 so that Nap can agree or push back to the next milestone.
- Create test cases for all new features or new edge cases
- Correct existing test cases to adress core change and new edge cases
- Address any new bugs/issues
- Address outstanding technical debt
- Print statements versus logging calls (log, info level with a caveat for debug statements that can be commented out)
- Commenting new functions and existing functions that are judged deficient or innacurate.
- Pass all tests in the Hudson test server (All kinds of errors at this point!) Somebody has been naughty!
- Completing the Changelog for new features and bug fixes and making a summary changelog for the roadmap.

Tag a Release Candidate, and repeat.

- Documenting new features in the wiki and normalizing the documentation top 1.0. Any additions from there would
be handled by graphical tags denoting the version where it was introduced. (like the MK site: Multisite, check_mk);
- Documenting existing features in the wiki (ex: duplicate_foreach, service templates on hosts, broker modules, shinken templates, customizing templates, skonf, retention(redis/memcached versus mongodb, etc.);
- Updating the web site: roadmap, features, Shinken versus Nagios, download links.

Once the list has been reviewed, these could all be converted individualy as issues for Milestone 1.0?