Clockwork is still very much a nascent bit of software. Consequently, its roadmap is focused on finishing out the core feature set and getting to a well-documented and stable first release.

Here's to 1.0.0!

Development Work Outstanding

Note: this section is a webified version of the TODO file found in the root of the Clockwork codebase; when in doubt (and if you're looking to jump in and start hacking) check there for the most up-to-date information.

The following features need to be implemented before Clockwork can be considered fully-functional:

  1. More Intrusive Certificate Verification
  2. Support Certificate Revocation through cwca
  3. Automatic Enrolment (keys + certificates) DONE
  4. Auxiliary Memory Tests DONE

Infrastructure and Hosting

If anyone has any suggestions for these, wants to write them, or has server space to donate, please contact us.

  1. Identify and Implement a Bug Tracker solution.
  2. Build Community Support tools:
    1. Mailing List(s)
    2. Forums
  3. Project Website (you're reading it now…)

Documentation Efforts

There are two forms of documentation that need to be fleshed out: man pages and the web-based stuff. Some of it does cross over — the man pages are also included on the website.

man Pages

Perhaps the most important set of documents, the man pages provide on-site guidance to system engineers and administrators in a format that is both familiar and useful. The man page source files are found in the Clockwork codebase under the man/ directory.

  1. clockwork.7 – Introduction to Clockwork – needs finished.
  2. cwpol.1 – Policy Explorer command reference – needs finished.
  3. cwdb.1 – Reporting reference – needs written.

The following web-based documentation is still outstanding:

  1. Quickstart Guide - needs written/reviewed
  2. All Things Clockwork - A Sysad's Guide - needs written/reviewed
  3. Developer's Handbook - needs written/reviewed

Release Plan

Clockwork is system software, and for shops that have implemented it for their configuration management needs, updating can be painful and scary.

For that reason alone, the Clockwork development team adheres to the when it's ready release methodology - a new stable release (version X.Y) is made when the features are mature, the regression tests pass 100%, and test code coverage is acceptable.

Version Numbering

Clockwork version numbers consist of three dot-separated decimal components, X.Y.Z.

The first number — X — is the major version number. It gets incremented when the architecture of Clockwork changes dramatically. All Clockwork builds with the same major version number interoperate (bugs notwithstanding).

The second — Y — is the minor version number. Minor releases are made to introduce new features into Clockwork without changing its architecture. Builds with the same major and minor version numbers are equivalent in terms of functionality.

The third number — Z — is the revision number. Revision releases address security issues and bugs. They do not introduce new features.

The Clockwork website is licensed under the Creative Commons Attribution-NoDerivs 3.0 United States License