I'm struggling to find a good release numbering scheme for annotateit. At the moment, I'm sticking with the common x.x.x numbering scheme, but it feels pretty arbitrary. I set targets for features that I want in annotateit, and when I achieve those targets, I bump the version number. But I'm not confident that those numbers actually signify anything to anyone.
One that I've seen that I think is fairly interesting is using the date of release in the filename of the distribution, but I don't think the dates convey enough information either. Maybe I need to settle on a hybrid release numbering scheme that would convey my opinion as to the reliability of the software, and the date it was released on. e.g. 0.20030728 might indicate a really unstable release, whereas 1.20030728 would indicate a more stable release.
CMM stands for Capability Maturity Model, not Code maturity model, as I had mistakenly assumed, and refers to the capabilities of the organization developing the software rather than the maturity of the software itself.
FOAF updates: Trust rankings are now exported, making the data available to other users and websites. An external FOAF URI has been added, allowing users to link to an additional FOAF file.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!