[Xastir] Stable release plus version numbering

[William McKeehan]

Are you going to fork the development tree and maintain the 1.10 version as
stable with patches?

If not, then I'd just go with 1.9.0 for the stable and 1.9.1 for the development.

Not sure what I would suggest for the next stable release; maybe it's time to
let 1.9 sit and begin real work on 2.0 ? ? ? ? (a boy can dream, can't he?)
-- 
William McKeehan

On Thu, March 29, 2007 9:46 am, Curt, WE7U wrote:
> On Wed, 28 Mar 2007, Jeremy Utley wrote:
>
>> As a non-developer I would agree with this as well.  Major changes
>> usually involve changes in the ABI/API that makes things incompatible
>> with the previous release, or large changes in the code base that
>> almost makes it an entirely new application.  For just the minor
>> changes that have been in CVS since the last stable release, it would
>> seem a bump in the minor version would be the most we should do here.
>
> In other words go to 1.10 instead of 2.0, and make the next devel
> version be 1.11?
>
> This might muck with the TOCALL a bit.  Right now we're sending
> APX185.  We'd need to send APX110 which would appear to be going
> backwards in our revisions.
>
> --
> Curt, WE7U.   APRS Client Comparisons: http://www.eskimo.com/~archer
> "Lotto:    A tax on people who are bad at math." -- unknown
> "Windows:  Microsoft's tax on computer illiterates." -- WE7U
> "The world DOES revolve around me:  I picked the coordinate system!"
> _______________________________________________
> Xastir mailing list
> Xastir at xastir.org
> http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
>