[Gdal-dev] Radical OGR Update
Daniel Morissette
dmorissette at dmsolutions.ca
Thu Feb 19 15:19:07 EST 2004
Frank Warmerdam wrote:
>
> Well, I for one was intimidated by the MapServer branches. I mostly just
> kept my head down and worked on the trunk. I'm not saying it is wrong for
> MapServer or other packages to manage branches. I'm just nervous about
> adding the conceptual overhead to GDAL.
>
Maybe I'm the only one who understands them?
It's simple:
After the MapServer 4.0 release we *branched* using the name
"branch-4-0", and after that all 4.0.z bugfix releases were and will be
*tagged* as "rel-4-0-z". So if you want to commit a fix to the stable
4.0 you "cvs update -r branch-4-0" and commit your fix. The main
developments for 4.1/4.2 happen in the main CVS trunk.
When we are ready to release MapServer 4.2 we'll do the same: create a
"branch-4-2" branch, and tag the releases as "rel-4-2-z".
I would propose that the same system could be used for GDAL.
>
> As far as I know, I can create a branch at any time against a particular
> tag, so it wouldn't necessarily have to be done in advance. Is that
> correct?
>
Good point. You can create a branch at any time.
>
> Do you have a concept of how much major version numbers cost? I am working
> on a budget here, not a big corporate environment like DM Solutions, flush
> with money. I pay for every version number out of my own pocket!
>
I realize that version numbers aren't cheap, but you can easily get
cheap 1.x/2.x version numbers these days since all the main software
vendors are up in the 6.x, 7.x, and even in the thousands. BTW, we've
also got some old 3.3.0xx versions from MapServer that we don't use any
more...they go as far as 3.3.011. I'm sure Steve Lime would contribute
them to GDAL for free as long as you're willing to make the next release
GDAL 3.3.
Daniel
--
------------------------------------------------------------
Daniel Morissette dmorissette at dmsolutions.ca
DM Solutions Group http://www.dmsolutions.ca/
------------------------------------------------------------
More information about the Gdal-dev
mailing list