« Return to Thread: Re: rc ping
Re: rc ping
by Guenther Meyer
::
Rate this Message:
Am Sonntag 10 Mai 2009 schrieb Hamish:
> 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?
>something like that...
> 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).
>
yes, 2-4 releases per year depending on progress and features.
bugfix releases as they are needed.
> > 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.
>
hmm, I think it's a little bit strange to habe thousands of 2.10pre versions
without having a final 2.10.
but looking just at the features, you may be right.
wasn't the "2.x" related to the gtk version?
after that, I was thinking of a 3.0 version too.
navigation will come, and a lot of other things have to be rewritten and
optimized...
_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive
> 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).
>
yes, 2-4 releases per year depending on progress and features.
bugfix releases as they are needed.
> > 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.
>
hmm, I think it's a little bit strange to habe thousands of 2.10pre versions
without having a final 2.10.
but looking just at the features, you may be right.
wasn't the "2.x" related to the gtk version?
after that, I was thinking of a 3.0 version too.
navigation will come, and a lot of other things have to be rewritten and
optimized...
_______________________________________________
GPSdrive mailing list
GPSdrive@...
http://lists.gpsdrivers.org/mailman/listinfo/gpsdrive
signature.asc (204 bytes) « Return to Thread: Re: rc ping
| Free embeddable forum powered by Nabble | Forum Help |
