[FOSSology] version number scheme proposal

[Matt Taggart]

Hi fossology,

I've been thinking about a version numbering scheme for FOSSology. I 
propose:

A.B.C

where

A = Major release number
    Reason for change:
      schema and/or agent API _breakage_
B = Minor release number
    Reasons for change:
      schema and/or agent APIs are _added_ or _extended_ 
      new agents added
      security fixes
      major roll up of bugfixes
C = Bugfix release number
    Reasons for change:
      any bugfix worth doing a new release/test cycle


We're probably on schema version zero or one, depending on how you like to 
count and how important a 1.0.0 version number is to you :)

We've talked about how we deliver schema changes. Under the above scheme: 
For a minor version number change we should be able to deliver a script 
that just extends the database schema. For a major version number change, 
we'd either have to ship a process that could convert the existing data to 
the new schema, or in some cases everything would need to be reloaded.

What do you think?

-- 
Matt Taggart
matt at lackof.org