Hi Project Steering Committee,
I'd like to make a motion to release GeoNetwork version 2.2.0 on Wednesday.
I am waiting for some small changes to GAST from Stefano that should fix some problems in the migration process. Simon, after release 2.2.0 we should discuss what we use to fix these issues in more detail. You made changes on trunk that Stefano is also looking at but that for now seem to be a bit deep to include in this release as you also indicated yourself earlier on.
Let me know if wednesday is OK for you al.
Ciao,
Jeroen
Hi Project Steering Committee,
I'd like to make a motion to release GeoNetwork version 2.2.0 on
Wednesday.
I am waiting for some small changes to GAST from Stefano that should
fix some problems in the migration process. Simon, after release 2.2.0
we should discuss what we use to fix these issues in more detail. You
made changes on trunk that Stefano is also looking at but that for now
seem to be a bit deep to include in this release as you also indicated
yourself earlier on.
Let me know if wednesday is OK for you al.
Ciao,
Jeroen
Hi Project Steering Committee,
I'd like to make a motion to release GeoNetwork version 2.2.0 on Wednesday.
I am waiting for some small changes to GAST from Stefano that should fix some problems in the migration process. Simon, after release 2.2.0 we should discuss what we use to fix these issues in more detail. You made changes on trunk that Stefano is also looking at but that for now seem to be a bit deep to include in this release as you also indicated yourself earlier on.
Hi Jeroen,
For sure the current fixes to avoid writing nulls need a deeper and long term fix such as adding type info to some of the JDBC calls.
If I understand you correctly, you're saying we go with the current fixes I applied to the trunk and do the deeper ones later? Sounds good to me - I guess I'd like someone else to test postgresql though as I found that the postgresql 7.4 jdbc3 drivers were the only ones that worked correctly with both gast and geonetwork on both postgresql 7.4 and 8.1 - the 8.x jdbc3 drivers seem to refuse to do things like cast string values to integer columns - causing problems for migrations in gast and possibly in other places too.
This raises the issue of whether we should replace the 8.x postgresql jdbc3 drivers in the trunk with the 7.4 postgresql jdbc3 drivers before the 2.2.0 release.
Hi Project Steering Committee,
I'd like to make a motion to release GeoNetwork version 2.2.0 on Wednesday.
I am waiting for some small changes to GAST from Stefano that should fix some problems in the migration process. Simon, after release 2.2.0 we should discuss what we use to fix these issues in more detail. You made changes on trunk that Stefano is also looking at but that for now seem to be a bit deep to include in this release as you also indicated yourself earlier on.
Let me know if wednesday is OK for you al.
Ciao,
Jeroen
Hi Project Steering Committee,
I'd like to make a motion to release GeoNetwork version 2.2.0 on
Wednesday.
I am waiting for some small changes to GAST from Stefano that should
fix some problems in the migration process. Simon, after release 2.2.0
we should discuss what we use to fix these issues in more detail. You
made changes on trunk that Stefano is also looking at but that for now
seem to be a bit deep to include in this release as you also indicated
yourself earlier on.
Let me know if wednesday is OK for you al.
Ciao,
Jeroen
I had casting problems too with pg jdbc drivers lately (even if not directly
related to GN). In the list no one replied to Simon, so we don't know how
much this problem is presenting to GN users.
If you think this is a minor issue, pls go on with the 2.2.0 release.
Ciao,
Emanuele
Alle 06:09:34 di martedì 1 aprile 2008, Simon Pigot ha scritto:
Jeroen Ticheler wrote:
> Hi Project Steering Committee,
> I'd like to make a motion to release GeoNetwork version 2.2.0 on
> Wednesday.
>
> I am waiting for some small changes to GAST from Stefano that should
> fix some problems in the migration process. Simon, after release 2.2.0
> we should discuss what we use to fix these issues in more detail. You
> made changes on trunk that Stefano is also looking at but that for now
> seem to be a bit deep to include in this release as you also indicated
> yourself earlier on.
Hi Jeroen,
For sure the current fixes to avoid writing nulls need a deeper and long
term fix such as adding type info to some of the JDBC calls.
If I understand you correctly, you're saying we go with the current
fixes I applied to the trunk and do the deeper ones later? Sounds good
to me - I guess I'd like someone else to test postgresql though as I
found that the postgresql 7.4 jdbc3 drivers were the only ones that
worked correctly with both gast and geonetwork on both postgresql 7.4
and 8.1 - the 8.x jdbc3 drivers seem to refuse to do things like cast
string values to integer columns - causing problems for migrations in
gast and possibly in other places too.
This raises the issue of whether we should replace the 8.x postgresql
jdbc3 drivers in the trunk with the 7.4 postgresql jdbc3 drivers before
the 2.2.0 release.
Thanks Emanuele,
Yes, it is an issue we have to watch closely. At the same time it seems to be working with an older postgres driver v7.4 according to Simon so it's not a full block. I'll include a description of the problem under Known issues in the release notes.
I'll go ahead with the release and we can resolve the issue completely in a next minor release if needed.
Ciao,
Jeroen
On Apr 1, 2008, at 9:07 PM, Emanuele Tajariol wrote:
+0
I had casting problems too with pg jdbc drivers lately (even if not directly
related to GN). In the list no one replied to Simon, so we don't know how
much this problem is presenting to GN users.
If you think this is a minor issue, pls go on with the 2.2.0 release.
Ciao,
Emanuele
Alle 06:09:34 di martedì 1 aprile 2008, Simon Pigot ha scritto:
Jeroen Ticheler wrote:
Hi Project Steering Committee,
I'd like to make a motion to release GeoNetwork version 2.2.0 on
Wednesday.
I am waiting for some small changes to GAST from Stefano that should
fix some problems in the migration process. Simon, after release 2.2.0
we should discuss what we use to fix these issues in more detail. You
made changes on trunk that Stefano is also looking at but that for now
seem to be a bit deep to include in this release as you also indicated
yourself earlier on.
Hi Jeroen,
For sure the current fixes to avoid writing nulls need a deeper and long
term fix such as adding type info to some of the JDBC calls.
If I understand you correctly, you're saying we go with the current
fixes I applied to the trunk and do the deeper ones later? Sounds good
to me - I guess I'd like someone else to test postgresql though as I
found that the postgresql 7.4 jdbc3 drivers were the only ones that
worked correctly with both gast and geonetwork on both postgresql 7.4
and 8.1 - the 8.x jdbc3 drivers seem to refuse to do things like cast
string values to integer columns - causing problems for migrations in
gast and possibly in other places too.
This raises the issue of whether we should replace the 8.x postgresql
jdbc3 drivers in the trunk with the 7.4 postgresql jdbc3 drivers before
the 2.2.0 release.
Oops - forgot to vote although I did use unofficial, alternative words like fine with me - I would've voted +0 similar to Emanuele - because I would've liked to resolve the postgresql drivers issue. But it wasn't a blocking issue, so a very late:
- I would've voted +0 similar to Emanuele - because I would've liked to resolve the postgresql drivers issue. But it wasn't a blocking issue, so a very late: