Using new SVN for PostGIS

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

Using new SVN for PostGIS

Mateusz Loskot
Hi,

I'm about to start back committing PostGIS FDO to my branch, and I'd
like to ask for recommended strategy regarding fdocore.

Currently, I work on PostGIS FDO using fdocore in r594, from 2006-12-11.
I see there has bene plenty of new changes made to the fdocore/trunk.
Now, should I update my copy of fdocore with current fdocore\trunk or
better with of of branches for 3.2 ?

Which version my PostGIS FDO will be reviewed and merged with,
let's say at the beginning of February ?

Best regards
--
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Reply | Threaded
Open this post in threaded view
|

RE: Using new SVN for PostGIS

Greg Boone
I am not sure I understand. Please correct me if I am wrong here. Are
you preparing to create your own SVN repository outside fdordbms? If so,
that is not the expected solution. We expect you to merge your changes
into the trunk of fdordbms and have PostGIS be an equal to the ODBC and
MySQL providers with a build process that builds all three. Therefore,
you would have to integrate any changes you made to fdocore or fdodbms
in order to support the PostGIS provider back into the respective
branches of these repositories.

Greg

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Mateusz
Loskot
Sent: Tuesday, January 16, 2007 2:42 PM
To: fdo-internals
Cc: Jason Birch
Subject: [fdo-internals] Using new SVN for PostGIS

Hi,

I'm about to start back committing PostGIS FDO to my branch, and I'd
like to ask for recommended strategy regarding fdocore.

Currently, I work on PostGIS FDO using fdocore in r594, from 2006-12-11.
I see there has bene plenty of new changes made to the fdocore/trunk.
Now, should I update my copy of fdocore with current fdocore\trunk or
better with of of branches for 3.2 ?

Which version my PostGIS FDO will be reviewed and merged with,
let's say at the beginning of February ?

Best regards
--
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Reply | Threaded
Open this post in threaded view
|

RE: Using new SVN for PostGIS

Greg Boone
In reply to this post by Mateusz Loskot
Correction:

"Therefore, you would have to integrate any changes you made to fdocore
or fdodbms in order to support the PostGIS provider back into the
respective *trunks* of the fdordbms and fdocore repositories."

Greg

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Greg Boone
Sent: Tuesday, January 16, 2007 4:07 PM
To: FDO Internals Mail List
Cc: Jason Birch
Subject: RE: [fdo-internals] Using new SVN for PostGIS

I am not sure I understand. Please correct me if I am wrong here. Are
you preparing to create your own SVN repository outside fdordbms? If so,
that is not the expected solution. We expect you to merge your changes
into the trunk of fdordbms and have PostGIS be an equal to the ODBC and
MySQL providers with a build process that builds all three. Therefore,
you would have to integrate any changes you made to fdocore or fdodbms
in order to support the PostGIS provider back into the respective
branches of these repositories.

Greg

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Mateusz
Loskot
Sent: Tuesday, January 16, 2007 2:42 PM
To: fdo-internals
Cc: Jason Birch
Subject: [fdo-internals] Using new SVN for PostGIS

Hi,

I'm about to start back committing PostGIS FDO to my branch, and I'd
like to ask for recommended strategy regarding fdocore.

Currently, I work on PostGIS FDO using fdocore in r594, from 2006-12-11.
I see there has bene plenty of new changes made to the fdocore/trunk.
Now, should I update my copy of fdocore with current fdocore\trunk or
better with of of branches for 3.2 ?

Which version my PostGIS FDO will be reviewed and merged with,
let's say at the beginning of February ?

Best regards
--
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals

_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Reply | Threaded
Open this post in threaded view
|

Re: Using new SVN for PostGIS

Mateusz Loskot
In reply to this post by Greg Boone
Greg Boone wrote:
> I am not sure I understand. Please correct me if I am wrong here. Are
> you preparing to create your own SVN repository outside fdordbms?
> If so, that is not the expected solution.

Definitely, I'm not going to go with my own repo.

> We expect you to merge your changes into the trunk of fdordbms and
> have PostGIS be an equal to the ODBC and MySQL providers with a build
> process that builds all three.

Yes, this is exactly how I'd like to merge too.

> Therefore, you would have to integrate any changes you
> made to fdocore or fdodbms in order to support the PostGIS provider
> back into the respective branches of these repositories.

That's right.


I'll try to ask this way:

I've been disconnected from the SVN changes in fdocore/trunk and
fdordbms/trunk for a ~1 month.

If I update my working copies and continue building PostGIS FDO
against current fdocore/trunk, and finally merge with fdocore/trunk and
fdordbms/trunk, which version of Autodesk Map 3D and MapGuide
can I target with my PostGIS FDO?

This question is important because as far as I know, fdocore has been
frozen at some point, for nearest release.

Will it be possible to use the PostGIS FDO with Map 3D Hammerhead ?


Cheers
--
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Reply | Threaded
Open this post in threaded view
|

Re: Using new SVN for PostGIS

Robert Bray-2
Mateusz,

For use with Hammerhead you want to be on FDO 3.2. Greg can clarify whether that should be 3.2.x or 3.2.0.

Bob

Mateusz Loskot wrote:
Greg Boone wrote:
  
I am not sure I understand. Please correct me if I am wrong here. Are
you preparing to create your own SVN repository outside fdordbms?
If so, that is not the expected solution.
    

Definitely, I'm not going to go with my own repo.

  
We expect you to merge your changes into the trunk of fdordbms and
have PostGIS be an equal to the ODBC and MySQL providers with a build
process that builds all three.
    

Yes, this is exactly how I'd like to merge too.

  
Therefore, you would have to integrate any changes you
made to fdocore or fdodbms in order to support the PostGIS provider
back into the respective branches of these repositories.
    

That's right.


I'll try to ask this way:

I've been disconnected from the SVN changes in fdocore/trunk and
fdordbms/trunk for a ~1 month.

If I update my working copies and continue building PostGIS FDO
against current fdocore/trunk, and finally merge with fdocore/trunk and
fdordbms/trunk, which version of Autodesk Map 3D and MapGuide
can I target with my PostGIS FDO?

This question is important because as far as I know, fdocore has been
frozen at some point, for nearest release.

Will it be possible to use the PostGIS FDO with Map 3D Hammerhead ?


Cheers
  


_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Reply | Threaded
Open this post in threaded view
|

RE: Using new SVN for PostGIS

Greg Boone
In reply to this post by Mateusz Loskot
Fundamentally, if you want to be officially 'integrated' with the build
of FDO that is supported in Map Hammerhead then you will have to drop
your changes in branches/3.2.x. (NOTE: You would also be required to
merge your changes into the trunk)

However, submitting into branches/3.2.x requires additional due
diligence. Does your submission affect any existing fdocore/fdordbms
*Windows* build processes, existing header files or source files? If so,
these files will need to be dropped ASAP using the Map/FDO defect
tracking/code submission mechanism.

If such changes are required send me the set of fdocore/fdordbms
existing/new files to be modified (as a zip file) and Robert and I will
determine the effect of making such changes. We will also determine if
the map team is willing to take these changes at this time. Once that
determination is made you would be free to integrate your changes.

If you drop only into the trunk and not the 3.2.x branch then we would
not be able to guarantee that the PostGIS provider would be supported
inside Map using FDO 3.2.x without further testing. Actually, I
seriously doubt that you would be supported in Hammerhead due to the Dec
18th change made by Brent Robinson

"Binary compatibility change to fdo.dll (trunk version)"

See attached file for details.

Greg

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of Mateusz
Loskot
Sent: Tuesday, January 16, 2007 4:34 PM
To: FDO Internals Mail List
Subject: Re: [fdo-internals] Using new SVN for PostGIS

Greg Boone wrote:
> I am not sure I understand. Please correct me if I am wrong here. Are
> you preparing to create your own SVN repository outside fdordbms?
> If so, that is not the expected solution.

Definitely, I'm not going to go with my own repo.

> We expect you to merge your changes into the trunk of fdordbms and
> have PostGIS be an equal to the ODBC and MySQL providers with a build
> process that builds all three.

Yes, this is exactly how I'd like to merge too.

> Therefore, you would have to integrate any changes you
> made to fdocore or fdodbms in order to support the PostGIS provider
> back into the respective branches of these repositories.

That's right.


I'll try to ask this way:

I've been disconnected from the SVN changes in fdocore/trunk and
fdordbms/trunk for a ~1 month.

If I update my working copies and continue building PostGIS FDO
against current fdocore/trunk, and finally merge with fdocore/trunk and
fdordbms/trunk, which version of Autodesk Map 3D and MapGuide
can I target with my PostGIS FDO?

This question is important because as far as I know, fdocore has been
frozen at some point, for nearest release.

Will it be possible to use the PostGIS FDO with Map 3D Hammerhead ?


Cheers
--
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals


Hi,

 

I will be checking in some modifications to the svn trunk that will change the binary compatibility for fdo.dll. Once this is done, if you update from the svn trunk and build the FDO project, you will also need to build your providers. The changes will likely go in on Monday, Dec 18.

 

The above does not affect the 3.2.x branch. The FDO binary compatibility will not change for this branch.

 

Brent.

 


_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals
Reply | Threaded
Open this post in threaded view
|

Re: Using new SVN for PostGIS

Mateusz Loskot
Greg Boone wrote:
> Fundamentally, if you want to be officially 'integrated' with the build
> of FDO that is supported in Map Hammerhead then you will have to drop
> your changes in branches/3.2.x. (NOTE: You would also be required to
> merge your changes into the trunk)

Yes, this is clear.

> However, submitting into branches/3.2.x requires additional due
> diligence. Does your submission affect any existing fdocore/fdordbms
> *Windows* build processes, existing header files or source files?

Yes, as we've already discussed and as it was today finally accepted,
I'm applying changes related to reserved column names / spatial context.

> If so, these files will need to be dropped ASAP using the Map/FDO defect
> tracking/code submission mechanism.

This week it should be fixed/teste, I hope.

> If such changes are required send me the set of fdocore/fdordbms
> existing/new files to be modified (as a zip file) and Robert and I will
> determine the effect of making such changes. We will also determine if
> the map team is willing to take these changes at this time. Once that
> determination is made you would be free to integrate your changes.

I understand. OK, after I apply discussed fixes I'll prepare the package.

> If you drop only into the trunk and not the 3.2.x branch then we would
> not be able to guarantee that the PostGIS provider would be supported
> inside Map using FDO 3.2.x without further testing. Actually, I
> seriously doubt that you would be supported in Hammerhead due to the Dec
> 18th change made by Brent Robinson

I see.

> "Binary compatibility change to fdo.dll (trunk version)"
> See attached file for details.

Right, I remember it.

OK I'll pursue fixes tomorrow and see if they are are big or not so big.

p.s Jason, I'm adding you to CC, both of your e-mails.

Cheers
--
Mateusz Loskot
http://mateusz.loskot.net
_______________________________________________
fdo-internals mailing list
[hidden email]
http://lists.osgeo.org/mailman/listinfo/fdo-internals