Re: rc ping

Guenther wrote:
> and then we should change the numbering scheme and release more often
> then, maybe every few month.

> I propose we just count on when new features are added  (2.11, 2.12,
> ...), and only add a minor number, when important fixes have  been
> applied (2.11.1, 2.11.2).

so break off a new branch at each 2.x release, and only ship 2.x.y
updates from those branches if nasty bugs are found and are easily
backported? and then stop supporting 2.x-1 with those bugfix updates
after the next 2.x.0 is released?

to avoid putting everyone on the upgrade treadmill but making sure the
official $(Ubuntu) package is always <= 3 months old, I'd vote for near-
quarterly releases (plan for 4/year, but accept 2-3 if things get slow).
The 2.x.y bugfix releases I wouldn't mind making monthly (as needed).


more releases are also nice deltas to test against if some regression is
introduced. but of course they do take a finite amount of work.


> requiring about five years to get from 2.09 to 2.10 is not
> what I expect for a piece of free software, that's almost continously
> developed... ;-)

Now that I think of it, we /could/ call the new release GpsDrive 3.0.
We haven't broken map tile compatibility, but enough has changed, been
removed, and has been added since 2.09 (or 2.10preX) that it doesn't seem
self-inflating to call it that.



Hamish



     

_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive