1. (done) Gabriel's code re-organization
2. (done) Solve some install issues
3. (done) Fixing some obvious bugs
4. (2 fail - 475 pass) Finish CITE WFS testing & fixing
5. (todo) PostGIS 1.0 WKB bug
6. (todo) PostGIS column escaping for PK
7. (todo) Bounds for tables w/o geometries. (dont know what the
behavior should be - "null"?)
8. (todo) NameSpace problem udigers reported
9. (todo) change how the packaging/installation is done
10. (todo) GEOSERVER_HOME -- perhaps in RC2?
If there's anything else you'd like to see in 1.3.0RC1 (and you can help
make it happen) please speak up!
I think we will have a 1.3.0RC2 (and perhaps RC3) before we go to 1.3.0.
Unfortunately, the releases will be a little later than expected, but
Geoserver is very rapidly improving in quality, functionality,
ease-of-use, and code organization.
Once this release is out, I'd really like people to download and test
(and to make sure that it runs correctly in a variety of different
containers).
This is simply a ui problem - the namespace "gml" should not be allowed as a "custom" namespace prefix. It is already taken as the namespace for the gml schema....
If there's anything else you'd like to see in 1.3.0RC1 (and you can help
make it happen) please speak up!
This may already be done, can check if the data url returned by the wms correctly points to the associated wfs request? This would allow udig to "edit" a wms layer (and would be a cool demo to have over mapserver).
I think we will have a 1.3.0RC2 (and perhaps RC3) before we go to 1.3.0.
Could we have one early next week (say tuesday?) for the end of the month udig crawl.
Unfortunately, the releases will be a little later than expected, but
Geoserver is very rapidly improving in quality, functionality,
ease-of-use, and code organization.
We understand And good news about the cite tests.
Once this release is out, I'd really like people to download and test
(and to make sure that it runs correctly in a variety of different
containers).
Can you set up a wiki page for that, so people can report back which containers work?
Jody
Did you finish your jts wkb reader? Is it in jts yet? Would be nice to
just use that.
6. (todo) PostGIS column escaping for PK
7. (todo) Bounds for tables w/o geometries. (dont know what the
behavior should be - "null"?)
8. (todo) NameSpace problem udigers reported
What's the problem?
9. (todo) change how the packaging/installation is done
10. (todo) GEOSERVER_HOME -- perhaps in RC2?
Could be wise. If this is too difficult we could just wait and tackle
it in geoserver 2.0/opensdi. But it would be nice to flesh it out now.
Are these all in JIRA? Do you have admin priveleges? James, could you
get them for David? Then you can schedule releases, create new
releases, and do more organization. Though I think you should be able
to at least schedule the bugs. Go ahead and create an rc2, and move
the bugs that we won't get for rc1 there. Also could be nice to put
the next release's open bugs in the wiki, like udig does.
Chris
If there's anything else you'd like to see in 1.3.0RC1 (and you can
help
make it happen) please speak up!
I think we will have a 1.3.0RC2 (and perhaps RC3) before we go to
1.3.0.
Unfortunately, the releases will be a little later than expected, but
Geoserver is very rapidly improving in quality, functionality,
ease-of-use, and code organization.
Once this release is out, I'd really like people to download and test
(and to make sure that it runs correctly in a variety of different
containers).
-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon
2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest
Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.
Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
And good news about the cite tests.