I'm pleased to announce the first beta release of libpion (0.2.0), a C++ development library for implementing lightweight HTTP interfaces. After two months of coding, I feel comfortable that the library now includes most of the functionality I set out to implement.

There are a few notable changes in this release. First, I have decided to release libpion using the Boost Software Licensecache:

• 0 = do not cache files in memory
• 1 = cache files in memory when requested, check for any updates
• 2 = cache files in memory when requested, ignore any updates

scan: (only applies to directories)

• 0 = do not scan the directory; allow files to be added at any time
• 1 = scan directory when started, and do not allow files to be added
• 2 = scan directory and pre-populate cache; allow new files
• 3 = scan directory and pre-populate cache; ignore new files

With the release of the first beta, this is probably as good a time as any to talk about libpion's version numbers. The version number is based on the format MAJOR.MINOR.BUILD, where:

• MAJOR = incremented whenever a major release is made (GA release will be "1")
• MINOR = incremented whenever minor functionality is added or changed
• BUILD = incremented for each MAJOR.MINOR release build

The MINOR number represents the stability of a particular MAJOR.MINOR branch. Odd numbers are considered "unstable" development branches while even numbers are considered "stable" release branches. Only bug fixes will be committed to the even "stable" branches, while the "unstable" odd branches are used for active development.

The BUILD number represents if the code is from a tagged, release build (even), or if the code is from a build made in between tagged releases (odd). An even build number is used for all public releases. An odd build number indicates that you have code containing patches made in between releases.

Consequently, the "0.2" branch is a "stable" one and only bug fix releases will be made to it. All new development will now move into a "0.3" branch.