In response to Andrea's request for regular status updates: - We have four new hires joining the AuScope/SISS/ASRDC team and are ramping up development. Will probably have four equivalent full time staff working on GeoServer.
- We have done some planning. One general point is GML 3.2 support which is not app-schema specific. We are dead keen to work on this in Q3 2010. Planning should be on geoserver.org when we firm this up. https://www.seegrid.csiro.au/twiki/bin/view/Infosrvices/GeoserverDevelopmentPlan2010 - Rini has just completed use case one for app-schema data type polymorphism (when properties vary in type across features): https://www.seegrid.csiro.au/twiki/pub/Infosrvices/GeoserverDevelopmentPlan2010/AuScope_-_WFS_Polymorphism_Use_Cases_-_v0.3.doc - I have implemented a GeoServer trunk build archive to allow longer availability of builds. See also the email at the end. Anyone can access this archive: https://www.seegrid.csiro.au/twiki/bin/view/Infosrvices/GeoserverAppSchemaDownloads - I am working on a new schema resolver (gt-app-schema-resolver) to allow catalog/classpath/cached-download of schemas. It will have no app-schema dependencies so be available for general use. It is intended to allow us to use schemas packaged in maven artifacts for unit testing, rather than obsolete schemas in svn. Cached schema downloads will greatly improve deployability. Kind regards, Ben. ------- Original Message -------- Subject: GeoServer build archive Date: Wed, 17 Mar 2010 14:24:10 +0800 From: Ben Caradoc-Davies <[email protected]> To: AuScope-dev mailing list <[email protected]> To facilitate quality control and deployment repeatability, I have established an archive to keep nightly snapshots of GeoServer trunk built by the Computational Geoscience buildbot. The official openplans.org nightly GeoServer trunk builds are similar in principle, but suffer from: (1) unit tests being turned off, and (2) only the most recent eight builds being kept. The new archive should remedy these defects by retaining an arbitrary number of builds, using the iVEC Petabyte Data Store. Archived builds can be subjected to quality control and recommended to deployers, who can then be sure that multiple deployments are all using the same build of GeoServer. Project managers should provision quality control testing of archived builds in their project plans, and report findings to other projects to assist their selection of deployment candidate builds. I welcome any feedback on the archive. The GeoServer trunk build archive: http://files.ivec.org/geoserver/geoserver-trunk/ The GeoServer app-schema download page now has a section on the archive: https://www.seegrid.csiro.au/twiki/bin/view/Infosrvices/GeoserverAppSchemaDownloads Implementation notes (cron and scripts, for Computational Geoscience internal users only): https://cg-twiki.arrc.csiro.au/twiki/bin/view/Compgeosci/GeoserverArchive Jira: https://cgsrv1.arrc.csiro.au/jira/browse/SISS-691 Kind regards, -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
