[Xastir] Stable release plus version numbering

[Tom Russo]

On Thu, Mar 29, 2007 at 10:12:25AM -0700, we recorded a bogon-computron collision of the <archer at eskimo.com> flavor, containing:
> On Thu, 29 Mar 2007, Tom Russo wrote:
> 
> > > In other words go to 1.10 instead of 2.0, and make the next devel
> > > version be 1.11?
> >
> > No, I was thinking more like the next stable release would be 1.9.0 and
> > the next devel snapshot would be 1.9.1, etc.
> 
> Which makes us non-compliant with the Release HOWTO.

Which part?  

Our devel snapshots are not releases.  Here's my thinking:

  1) A major release is a big deal, like changing the structure of the code,
     refactoring APIs etc.
  2) A minor release just adds features that are not transformational and
     that maintain a stable API from the last major release.
  3) A patch is just a set of bug fixes.

The last two seem to match our "stable" and "devel snapshots" pretty well.
So my scheme is wholely compatible with the release HOWTO, which is a set of
guidelines, not a set of hard rules.

I say we try to make our numbering system compatible with that described in
the HOWTO, but apply the following section to ourselves vigorously:

    3.2. But respect local conventions where appropriate

-- 
Tom Russo    KM5VY   SAR502   DM64ux          http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick