[fdo-internals] fdogdal <Bounds> support for 3.2.x

[Traian Stanev]

I agree with that. Each provider should have its own version number.


-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Haris
Kurtagic
Sent: Thursday, June 14, 2007 2:38 AM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] fdogdal <Bounds> support for 3.2.x

I think it is very important to get latest GDAL included into MapGuide
1.2, even if it means new FDO version or delay for MapGuide 1.2.

BTW:
In current process changes in provider are tied to version change of FDO
even FDO itself hasn't been changed.
If some provider has improvements I don't see it as a new version of
FDO.
I am thinking if it would be better that providers has its own
version's.

Haris

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: 14. junij 2007 0:23
To: FDO Internals Mail List
Subject: RE: [fdo-internals] fdogdal <Bounds> support for 3.2.x

I think we need to start a dialog with our primary client for the
branch, MapGuide OpenSource and see how they wish to proceed. 

Options:

1) Have a 3.2.3 release from 3.2.x
2) Branch 3.2.x and release from the new branch
3) Issue a special service pack instead of a full release.
4) ....

Greg

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org
[mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Frank
Warmerdam (External)
Sent: Wednesday, June 13, 2007 2:18 PM
To: FDO Internals Mail List
Subject: [fdo-internals] fdogdal <Bounds> support for 3.2.x

Folks,

I have prepared a patch implementing <bounds> support in the config file
for the fdogdal provider.  Jason has done some testing, and verified it
substantially improves performance in cases where many files are used
for
a single layer in MapGuide.

I have prepared a ticket with the patch, and I am seeking permission to
apply it to fdogdal's 3.2.x branch.

Do we intend to have an fdo 3.2.3 release?  If so, I think we should
create
a corresponding milestone in Trac, and I would see this going into that.
In the meantime, it would be possible to compile a custom
GRFPProvider.dll
against 3.2.x and use it with mapguide 1.2.0 (with fdo 3.2.2).

How shall we decide to handle such relatively substantial changes in our
stable branches?  A vote of the PSC?

   http://trac.osgeo.org/fdo/ticket/87

Best regards,
-- 
---------------------------------------+--------------------------------
------
I set the clouds in motion - turn up   | Frank Warmerdam,
warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | President OSGeo,
http://osgeo.org

_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals