Licorn developer documentation

Licorn Architecture in a nutshell

NOTE: this is the old architecture. I'm currently revamping all schemas for WMI2 new features and architectural reorganization. Everything should be ready for March 5th 2012.

• Modules (migration from HST)?
• CLI commands (migration from HST)?

Essentials

• Don't forget to start at  docs.licorn.org, this is the place of the current documentation.
• Foundations?
• Core?
• Interfaces?
• Daemon
• Extensions?
•  Backends
• TestSuite?

Contribs

• Contribs?

Versions of Licorn

Summary

[to be revised; see milestone names for current details, bugfixes releases are clearly indicated]

• odd versions are considered unstable, or in development, or testing. This is the case of versions 1.6.1.*, like 1.6.1.r594 and 1.6.3.r602. The r602 part is the corresponding revision up to which the code has been merged from in a given package.
• even version are considered stable. This is the case of version 1.6.2.0 (which corresponds to milestone 1.6.2), 1.6.2.1 and after.
• even version whith 4 numbers (1.6.2.1, 1.6.2.2, 1.6.2.3 and after) are considered bugfix releases.
• the third number (e.g. 2 in 1.6.2) indicate new functionnalities when it is incremented. In opposition, bugfix releases do not integrate any new functionnalities.
• generally speaking, blocker bugs that need new functionnalities to be completely fixed will not be fixed in bugfix releases. They will wait until next major release (here 1.6.4). There are some exceptions when a blocker bug only affect a very small subset of functionnalities or code, but this is documented in the comments of the bug, shows up in the timeline, and is announced by e-mail).

Overall code stability

Because milestones integrate tickets of bugs to be fixed, they should be considered stable when they are released. This means that version 1.6.2.0 is very stable and users of version 1.6.0.22 shouldn't have to wait until 1.6.2.1 or more to begin using the new version in production.