Re: [Ming-dev] 0.4 branch and head

[Stuart A. <and...@ne...>]

To avoid having to double commit everything, let's just let the HEAD be 0.4.4.
When something comes along that would be a new feature instead of just a bug
fix, we'll make a branch for 0.4.4 (And maybe even cut a release), and go
back to letting HEAD be 0.5.

This is being a little bit sloppy, but the rate of change seems to be low
enough right now that I don't really see it being a problem.


On Sat, 5 Jun 2010, strk wrote:

> Stuart,
> do you plan to continue maintaining the 0.4 branch of Ming ?
> I'm asking because I'm only committing to HEAD at the moment
> and we should bump the version numbers to tell HEAD apart
> from last release.
>
> So, if 0.4 is to be continued we should bump HEAD to 0.5
> and branch to 0.4.4, otherwise we'll bump HEAD to 0.4.4.
>
> I don't plan to do any major development in HEAD myself,
> just bug fixes, and some are already committed in HEAD and
> missing from branch (see ChangeLog).
>
> --strk;
>
>  ()   Free GIS & Flash consultant/developer
>  /\   http://strk.keybit.net/services.html
>


                                 Stuart

Stuart R. Anderson                               and...@ne...
Network & Software Engineering                   http://www.netsweng.com/
1024D/37A79149:                                  0791 D3B8 9A4C 2CDC A31F
                                                  BD03 0A62 E534 37A7 9149