Added by James Macgill, last edited by Gabriel Roldán on Oct 03, 2008  (view change)

Labels:

Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

These instructions explain how to create a Geotools release.

The instructions are meant for those making a formal milestone, a release candidate, a final release, or a point release of the Geotools project itself. However, the instructions can also be used by any project or anyone that needs to make their own release, for example to use a new release with [GeoServer ] or uDig.

Do not use the Maven "release" plugin

The instructions in this page invoke "svn copy", "mvn install" and "mvn deploy" manually. Those operations were supposed to be done automatically by "mvn release", but the later appears to be a difficult experience. It is time consuming (in case of failure, every new attempt implies a new checkout from svn), clobbers every pom.xml files by stripping comments and enumerating all possible versions of each maven plug-in (a lot), advances version number in a way that is not what we would like, make it difficult to use a javadoc tool more recent than javac, etc.

Invoking "svn copy", "mvn install" and "mvn deploy" explicitly is both faster and safer than "mvn release", since it allows human checks before to continue to the next step and avoid to redo some successful steps after a problem occured and has been fixed.

Must use Maven 2.0.8

Due to bugs various versions, including 2.0.6 and 2.0.7 you must use Maven 2.0.8 to perform the release (version 2.0.5 is known to work too, at the time of writing 2.0.8 is the latest available release)

Before You Start

Know the version numbers

You will need to know the version number of the release you wish to make as well as the version number of the next release that will be made. The former is needed to correctly name the files being released; the latter is needed to add a new task in the JIRA issue tracker so all tasks which are still open move up to be addressed in the next version.

Time and Space Requirements

The release process will take a few hours of time, will require a Gigabyte of free diskspace, and requires continuous network access.

Software and Environment Requirements


Check quickly that you are using the java and maven versions required:

Java

Geotools currently uses the JDK 1.5 version of Java(tm). The build will also need all the dependencies, presented earlier in this manual, which are required to build Geotools.

java -version

Should give, for example: 1.5.0_11

Use a 1.4 JDK when Releasing GeoTools 2.4 and earlier

Geotools releases must be made with a 1.4 JDK and not with a 1.5 JDK in compatibility mode. There are enough subtle glitches in the latter case that we run into many user problems.

java -version

should give, for example: 1.4.2_13

Even with the above JDK 1.4 warning for GeoTools 2.4 you will need to make an exception when generating javadocs. We need a more recent JDK in order to take advantage of latest javadoc tools improvements.

Maven 2

The build process uses Maven 2

Please use exactly this version
Maven 2.0.9

To check:

mvn --version

should give, for example: 2.0.5

Be sure to provide enough memory to Maven, if not already done:

export MAVEN_OPTS=-Xmx512M

Permissions

You will need access to several accounts and to the machines at refractions to properly create and announce the release.

Subversion Access to svn.geotools.org

You will need a Subversion account in order to properly create a release. Your account name/password is used to create tags and so on. Contact someone from admin@refractions.net if something is wrong with your account.

WebDAV Access to lists.refractions.net

The jars get uploaded to the maven area on lists.refractions.net during the deploy phase. Those jars will then be pulled in by those running maven.

The account name and password for lists.refractions.net are stored in the settings.xml file (located in your user folder ~/.m2/settings.xml). The file can remain indefinately and,if it is still in the same place, the file will be used during a future release.

<settings>
  <servers>
    <server>
      <id>refractions</id>
      <username>username</username>
      <password>...</password>
    </server> 
    <server>
      <!-- For web site (Maven reports) only; optional otherwise -->
      <id>geotools-fr</id>
      <username>username</username>
      <password>...</password>
    </server>
  </servers>
</settings>

Optional WebDAV Access to maven.geotools.fr

maven.geotools.fr is a mirror, and is also where the web site get sent from the site:deploy target. You don't need access to this folder if you don't plan to deploy the web site. As shown above, the username and password are added to the same settings.xml file.

Administration rights on the Geotools sourceforge site.

This will be required to upload the finished files and to create the download page for the release.

First make sure you have a sourceforge account. You can create an account if you need to. Then you need to join the geotools project and ask one of the other administrators to give you administration rights on the project.

Adminstration rights to Geotools Confluence, JIRA and codehaus xircles.

The JIRA authority is required to create a new release number for the future, to bump all unfinished tasks to that future release, and thereby to collect a list of changes in the current release.

The Confluence edit permission is required to make a release page.

The codehaus xircles login is now required for the previous two. See the bottom of the Geotools home page for instructions on how to obtain these permissions.

Obtain a clean code base

The code tree used for the build should be up to date and clean of any local modifications. This can be done by doing an update and making sure there are no significant local changes. First, change the default directory according the release to be performed:

  • If releasing a milestone (e.g. 2.4-M0) or the first release candidate (e.g. 2.4-RC0), cd trunk.
  • If releasing a release candidate other than the first one or a final release (e.g. 2.4.0), cd branches/2.4.x.

The default directory should contains the main pom.xml file. Then update the local repository and note the revision number returned by svn update (you will need it later).

svn update
svn status

The second of these should immediately return with a blank line. If there are local modifications or files that svn does not track, you may get something resembling the following:

$ svn status
?      testData
?      release.properties
?      plugin/arcsde/.classpath
?      plugin/arcsde/.project
?      plugin/arcsde/.settings

These modifications should not hurt, but you may want to wipe them out for safety. If there is pending modifications in files tracked by svn, you should commit them (after making sure that they do not break the build) before to continue. Take note again of the new revision number given by svn.

Test extensively the code base

This is to make sure there are no previously built classes still hanging around.

mvn clean

This is the build that will stress the library as much as possible to see if we can break things. The interactive.tests profile will open and close a series of windows as part of its work. 

mvn -Pextensive.tests,interactive.tests install
Check your network settings

If you're connected to the internet through DHCP and the DHCP server is providing your hostname, ensure your hostname matches the one in /etc/hostname and you have an entry in for it in /etc/hosts, or the coverage module tests will fail.

If there is any build or test failure, report the errors on the geotools developers mailing list (attach the appropriate file from the target/surefire-reports directory to the email) and wait until those errors are fixed. Then perform a new svn update, note the revision number and try again the above-cited mvn install command.

Preparing the Release


The release preparation will create a tag, change the version numbers, build the library and perform the full testing of the library to set everything up for release.

Create the branch (if needed) and the tag

The tag name must be the same than the Geotools version to be released. The following instructions assume that we are releasing Geotools 2.4-M0. For other releases, update the version number accordingly.

You will need the revision number from latest svn update. The following examples use revision number 24652, but this number needs to be replaced by the one provided by svn. We use the revision number in order to create a branch or a tag from the revision tested above. If some changes were commited after the latest successful mvn install, they will not be part of this release.

Perform only one of the following "svn copy" commands:

If releasing a milestone (e.g. 2.4-M0)

Creates the tag directly from the trunk:

svn copy http://svn.geotools.org/trunk/gt
         http://svn.geotools.org/tags/2.4-M0
         -m "Created 2.4-M0 tag from revision 24652." -r 24652

If releasing the first release candidate (e.g. 2.4-RC0)

First creates the branch, then the tag:

svn copy http://svn.geotools.org/trunk/gt
         http://svn.geotools.org/branches/2.4.x
         -m "Created 2.4.x branch from revision 24652." -r 24652

svn copy http://svn.geotools.org/branches/2.4.x
         http://svn.geotools.org/tags/2.4-M0
         -m "Created 2.4-RC0 tag."

If releasing candidate other than the first one, or final release (e.g. 2.4.0)

Creates the tag from the branch:

svn copy http://svn.geotools.org/branches/2.4.x
         http://svn.geotools.org/tags/2.4-M0
         -m "Created 2.4-M0 tag from revision 24652." -r 24652

Verify that the tag has been correctly created by visiting the http://svn.geotools.org/tags/ web page.

Change version number

After creation, please checkout the new tag:

cd ../tags
svn checkout http://svn.geotools.org/tags/2.5-M2/
cd 2.4-M0

You could also just "switch" your existing directory to the new tag:

svn switch http://svn.geotools/org/tags/2.5-M2

From this point, all remaining operations in this page should be performed from this tag directory (unless you're releasing from a stable branch). You should not need to change directory anymore (except for zipping javadoc). The next step is to replace every occurences of 2.4-SNAPSHOT by 2.4-M0 in all pom.xml files.

find . -name "pom.xml" -exec sed -i -e 's/<version>2.4-SNAPSHOT</<version>2.4-M0</' \{} \;

If you do not have Unix commands or are not confortable with sed, you can use the following Ant file instead. The file can also be found in the build/scm/ directory. Edit the 2.4-SNAPSHOT and 2.4-MO version numbers, save in a file named rename.xml in the tags/2.5-M1 directory and run ant -f rename.xml from the command line.

<?xml version="1.0" encoding="ISO-8859-1"?>
<project name="Rename" default="rename">
  <target name="rename">
    <replace dir=".">
      <include name="**/pom.xml"/>
      <replacefilter token="&lt;version&gt;2.4-SNAPSHOT&lt;/version&gt;"
                     value="&lt;version&gt;2.4-M0&lt;/version&gt;"/>
    </replace>
  </target>
</project>

Edit the GeoTools.java source file: there's a java source file in the referencing module that has a hardcoded version number, edit it with your text editor of preference (vi?) to make the VERSION constant match the version you're about to release.
eg,

$vi modules/library/metadata/src/main/java/org/geotools/factory/GeoTools.java

and turn

private static final Version VERSION = new Version("2.5-RC1");

into

private static final Version VERSION = new Version("2.5.0");

as appropriate for the version in question.

Check that the version numbers were updated as expected:

svn status
svn diff

Do not commit yet. We will commit only after a successful build from the tag directory.

Fixing number change error

If the numbers are not changed like expected (for example because of a mistake while using sed), revert the changes:

svn revert . --recursive

Then run again sed or ant, and check with svn diff.

If you're releasing from a stable branch, the branch version numbers must be updated as well. If, for example, the branch version number was 2.4.1-SNAPSHOT, you'll have to alter all pom file to state 2.4.2-SNAPSHOT instead. So:

  1. enter the branch checkout directory;
  2. rename;
  3. check the rename was done properly;
  4. commit;
  5. go back to the tag checkout;

Get those SNAPSHOT dependencies out of our build

At the current time their is one usual suspect - geoapi. Ask them to deploy something (example 2.1-M4) ... and then update as follows:
BEFORE (under root pom.xml dependency management tag):

<dependency>
         <groupId>org.opengis</groupId>
         <artifactId>geoapi-nogenerics</artifactId>
         <version>2.1-SNAPSHOT</version>
       </dependency>

AFTER

<dependency>
         <groupId>org.opengis</groupId>
         <artifactId>geoapi-nogenerics</artifactId>
         <version>2.1-M4</version>
       </dependency>

Build and Test Extensively

We already tested the library before to create the tag, so testing again here is more a safety measure; it should give the same result. Note that there is no need to invoke "mvn clean" since we are building from a fresh checkout.

mvn -Pextensive.tests,interactive.tests install

In case of build failure, report to the Geotools developers mailing list as we did for the build on trunk. If the build is successful, commit the pending version number changes. We commit only now because the tests after the version number change may reveal some bad configurations in pom.xml files, which should be fixed before the commit.

svn status
svn commit -m "Changed version number from 2.4-SNAPHOT to 2.4-M0."

Update the README

The skeleton README contains tags which must be updated to reflect the release. These tags include:

@VERSION@ geotools version
@DATE@ release date
@REQUIRED@ list of required modules (all those located in modules/library)
@PLUGIN@ list of plugins (all those located in modules/plugin)
@EXTENSION@ list of extensions (all those located in modules/extension)
@DEMO@ list of demos (all those located in demo)
@UNSUPPORTED@ list of unsupported modules (all those located modules/unsupported)

Substitute the appropriate values for in the file and then commit it. Remember, you are committing to the tag and not the development branch.

svn status
svn commit -m "Updated README for 2.4-M0."

Performing the Release

Deploy the jar files to the Maven repository. You can verify during the process if the files are uploaded as expected by watching the http://lists.refractions.net/m2/org/geotools/gt2-metadata/ web page (the Geotools metadata module should be among the first ones to be uploaded).

mvn deploy -Dmaven.test.skip=true
Not Authorized

If you run into problems deploying the jars to lists.refractions.net:

    [INFO] ------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    WARNING: No credentials available for the 'GEOTOOLS' authentication realm at lists.refractions.net

Ensure that you have provided the correct credentials in your settings.xml file.

If this step fails for some other reason after getting started, it may be caused by some network problem. Try running "mvn deploy" again.

Assemble the Distribution Archives

Now we need to create the binary, source and javadoc archives that users can download.

Assemble the Bin and Source Archives

We use the maven 2 assembly plug-in to do this for us.

mvn -Dmaven.test.skip=true assembly:assembly

If you look in target/ directory, you will see source and binary zip files.

Clean Up the Bin Archive

Remove unnecessary jars from the bin archive. This includes velocity and junit jars, as well as any jdbc driver stubs.

cd target
unzip gt2-2.4-M0-bin.zip
cd gt2-2.4-M0
rm -rf junit-*.jar
rm -rf velocity-*.jar
rm db2jcc_dummy-*.jar
rm gt2-sde-dummy-*.jar
cd ..
rm gt2-2.4-M0-bin.zip
zip -r gt2-2.4-M0-bin.zip gt2-2.4-M0

Assemble the Javadocs

This will use the standard Maven javadoc plugin to create the javadocs. The javadoc build uses Java 5 constructs, thus it is recommanded to build it with a more recent JDK than 1.4. The build creates a slew of warnings (13000+) and errors (100) and may exits with an error code. Nonetheless, the build produces the document tree. If you experience building problems, check out the GeoTools javadoc page too.

mvn javadoc:javadoc

Bundle the files by hand:

cd target/site/
zip -9 -r ../gt2-<put version here>-doc.zip apidocs/
cd ../..

Note: The javadoc plugin usage and configuration is explained in more details there.

Test the src release

  1. Unzip the gt2-yourreleaseversion-src.zip archive to a clean directory.
  2. Move or rename your <usrhome>/.m2/repository directory.
  3. Run maven from the root of the directory you unzipped to - mvn install

We do this in case a required module was accidentaly excluded from the list of modules to be included in the release. You would see no error during the release process but the generated src archive would be un-buildable.

Release to Public

Export out the User Guide

  1. Login to confluence and visit the user guide: http://docs.codehaus.org/display/GEOTDOC/Home
  2. go to the Browse Space > Advanced
  3. Choose Export Space
  4. Select HTML and don't include the comments
  5. It will take a few momemnts for the zip file to be ready
  6. Rename this zip to gt-2.5.0-guide.zip for later upload

Update JIRA and create a changelog

Any unresolved issues that did not make the release version need to be bumped back to the next release. Fortunately, JIRA allows you to do this en masse:

  • create the next 2.4.n+1 release
  • release 2.4.n
  • it will ask you where you want to move unresolved issues
    • select 2.4.n+1

This will update the changelog file to show what has been fixed since the last release. For example, see:
change log

Upload Distribution to SourceForge

SourceForge now allows various methods for uploading files:

  • web form
  • WebDav
  • sftp
  • rsynch + ssh

Details on how to use them can be found in the upload support guide, beware that the first two, thought easier, are recommended for uploads of less than 20MB.

Command-line client on Linux using sftp
sftp youUserName@frs.sourceforge.net
cd uploads
put gt2*.zip
Optional OpenOffice addin

You can optionally upload the OpenOffice addin. Current version provides only Geotools functionalities related to coordinate transformations, so changes in this addin are less frequent than the Geotools library as a whole and may not need to be uploaded for every releases. It addition, in may be safe to test the addin in an OpenOffice document before to make a new release.

Command-line clients
lcd ../modules/extension/openoffice/target
mput *.oxt

Then punt the release onto the geotools2 download page:

  1. Login to http://sourceforge.net/projects/geotools.
  2. Create a file release within that package, for this specific release and attach the file(s) you uploaded to that file release.
    1. Change processor to Platform-Independent
    2. Change file type to .zip, except gt2-version-src.zip which is source .zip, and the OpenOffice oxt file (if uploaded) which is Other Binary Package.
    3. Copy and pase the Release Notes from from README.txt
    4. Use the following form to generate a changelog:
      http://jira.codehaus.org/secure/ConfigureReleaseNote.jspa?projectId=10270
  3. Shadow your end-user: download your released files and verify their integrity; walk through an install to verify proper, expected operation.

As the last sanity check email the geotools2 list and ask people to try it out.

Update the Downloads Page

  1. Navigate to the Downloads Page.
  2. Press Add Child Page
  3. Enter in the title of the release (it is important to use '.' and '-' correctly for the sorting order)
    • 2.3-M1 - for a milestone release - adding a planned feature from a RnD branch
    • 2.3-RC3 - for a release candidate - feature complete, waiting on bug fixes, documentation, QA checks
    • 2.2.0 - for a major release - a formal release we API commited to supporting (supporting stable GeoServer or uDig)
    • 2.2.1 - for a patch release - remember that support, this is an example of a bug fix patch going out
  1. Press the 'select a template page' link and choose Geotools Release from the list
  2. Press next to view the generated page
  3. You will need to correct the following information:
    • Update the date (between the excerpt macros).
    • Update the Source forge links above to reflect the release by following this link.
      (The release name serves as the link for the Readme notice)
    • Update the Release Notes by choosing the the correct version from this link.

Tell the World

After the list has had a chance to try things out - Make an Announcement (you can edit that link to change all the examples)

geotools-devel@lists.sourceforge.net
  1. Post a message to the geotools-devel list.
  2. To: geotools-devel@lists.sourceforge.net
  3. Subject: Released
  4. Text:

    The GeoTools 2.5 release is available for download:

    The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is centered around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and will allow the library to evolve into supporting complex data structures.

    GeoTools 2.5 also targets graduation as an OSGeo (The Open Source Geospatial Foundation) project, and includes usability and performance improvements, preview version for the new Swing Widgets, and online and downloadable User Guide, an ISO 19107 Geometry implementation available as a supported module, new GPX DataStore, a much more robust ArcSDE DataStore, and JAXB Bindings for xml marshaling of GeoAPI ISO-19115 metadata structures.

    Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea and Justin who spent some time making the switch to the GeoAPI Feature Model passing GeoServer CITE tests, and to Jody for improving our build system.

    Not to forget, a big thanks to Geomatys, GeoSolutions, Refractions Research, OpenGeo and the community for continuously leveraging the project and making it such a success every day!

    Features from 2.5-RC0:

    • Feature Model switch to GeoAPI completed with passing CITE tests from GeoServer as sanity check
    • Some major bug fixes related to raster coverage rendering, ArcSDE, and Filter to SQL simplification
    • Build system improvements

    Features from 2.5-M3:

    • OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
    • Usability and Performance improvements to the Feature
    • FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

    Features from 2.5-M2:

    • JAXB bindings for the metadata module (ie support for ISO 19139 documents)
    • FeatureAccess super class for DataStore, allowing data access using ISO

    Features from 2.5-M1:

    • Change over to GeoAPI SimpleFeature
    • Support GetGMLObject
    • Preview of new Swing Widgets (and a warm welcome to Eclesia)

    Features from 2.5-M0:

    • Online User Guide
    • Java 5
    • Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
    • ISO 19107 Geometry implementation available as a supported module
    • DB2 returns to supported status
    • ArcSDE returns to supported status
    • GeometryBuilder utility class
    • A new GPX DataStore

    Release Notes:

    For more information please visit:

    If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

    Enjoy,
    The GeoTools Community

http://geotools.org/
  1. Add a news article: using Add News
  2. News Title: " released"
  3. Content: allows wiki links (example)

    The GeoTools 2.5 release is available for download:

    The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is centered around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and will allow the library to evolve into supporting complex data structures.

    GeoTools 2.5 also targets graduation as an OSGeo (The Open Source Geospatial Foundation) project, and includes usability and performance improvements, preview version for the new Swing Widgets, and online and downloadable User Guide, an ISO 19107 Geometry implementation available as a supported module, new GPX DataStore, a much more robust ArcSDE DataStore, and JAXB Bindings for xml marshaling of GeoAPI ISO-19115 metadata structures.

    Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea and Justin who spent some time making the switch to the GeoAPI Feature Model passing GeoServer CITE tests, and to Jody for improving our build system.

    Not to forget, a big thanks to Geomatys, GeoSolutions, Refractions Research, OpenGeo and the community for continuously leveraging the project and making it such a success every day!

    Features from 2.5-RC0:

    • Feature Model switch to GeoAPI completed with passing CITE tests from GeoServer as sanity check
    • Some major bug fixes related to raster coverage rendering, ArcSDE, and Filter to SQL simplification
    • Build system improvements

    Features from 2.5-M3:

    • OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
    • Usability and Performance improvements to the Feature
    • FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

    Features from 2.5-M2:

    • JAXB bindings for the metadata module (ie support for ISO 19139 documents)
    • FeatureAccess super class for DataStore, allowing data access using ISO

    Features from 2.5-M1:

    • Change over to GeoAPI SimpleFeature
    • Support GetGMLObject
    • Preview of new Swing Widgets (and a warm welcome to Eclesia)

    Features from 2.5-M0:

    • Online User Guide
    • Java 5
    • Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
    • ISO 19107 Geometry implementation available as a supported module
    • DB2 returns to supported status
    • ArcSDE returns to supported status
    • GeometryBuilder utility class
    • A new GPX DataStore

    Release Notes:

    For more information please visit:

    If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

    Enjoy,
    The GeoTools Community

geotools-gt2-users@lists.sourceforge.net

Let the user list know:

  1. To: geotools-gt2-users@lists.sourceforge.net
  2. Subject: Released
  3. Text:

    The GeoTools 2.5 release is available for download:

    The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is centered around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and will allow the library to evolve into supporting complex data structures.

    GeoTools 2.5 also targets graduation as an OSGeo (The Open Source Geospatial Foundation) project, and includes usability and performance improvements, preview version for the new Swing Widgets, and online and downloadable User Guide, an ISO 19107 Geometry implementation available as a supported module, new GPX DataStore, a much more robust ArcSDE DataStore, and JAXB Bindings for xml marshaling of GeoAPI ISO-19115 metadata structures.

    Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea and Justin who spent some time making the switch to the GeoAPI Feature Model passing GeoServer CITE tests, and to Jody for improving our build system.

    Not to forget, a big thanks to Geomatys, GeoSolutions, Refractions Research, OpenGeo and the community for continuously leveraging the project and making it such a success every day!

    Features from 2.5-RC0:

    • Feature Model switch to GeoAPI completed with passing CITE tests from GeoServer as sanity check
    • Some major bug fixes related to raster coverage rendering, ArcSDE, and Filter to SQL simplification
    • Build system improvements

    Features from 2.5-M3:

    • OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
    • Usability and Performance improvements to the Feature
    • FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

    Features from 2.5-M2:

    • JAXB bindings for the metadata module (ie support for ISO 19139 documents)
    • FeatureAccess super class for DataStore, allowing data access using ISO

    Features from 2.5-M1:

    • Change over to GeoAPI SimpleFeature
    • Support GetGMLObject
    • Preview of new Swing Widgets (and a warm welcome to Eclesia)

    Features from 2.5-M0:

    • Online User Guide
    • Java 5
    • Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
    • ISO 19107 Geometry implementation available as a supported module
    • DB2 returns to supported status
    • ArcSDE returns to supported status
    • GeometryBuilder utility class
    • A new GPX DataStore

    Release Notes:

    For more information please visit:

    If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

    Enjoy,
    The GeoTools Community

Open Source Geospatial Foundation

Directions:

  1. Post a message to the osgeo news email list (you are subscribed cause you are a nice caring PMC, right?).
  2. To: news_item@osgeo.org
  3. Subject: Released
  4. Text:

    The GeoTools 2.5 release is available for download:

    The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is centered around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and will allow the library to evolve into supporting complex data structures.

    GeoTools 2.5 also targets graduation as an OSGeo (The Open Source Geospatial Foundation) project, and includes usability and performance improvements, preview version for the new Swing Widgets, and online and downloadable User Guide, an ISO 19107 Geometry implementation available as a supported module, new GPX DataStore, a much more robust ArcSDE DataStore, and JAXB Bindings for xml marshaling of GeoAPI ISO-19115 metadata structures.

    Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea and Justin who spent some time making the switch to the GeoAPI Feature Model passing GeoServer CITE tests, and to Jody for improving our build system.

    Not to forget, a big thanks to Geomatys, GeoSolutions, Refractions Research, OpenGeo and the community for continuously leveraging the project and making it such a success every day!

    Features from 2.5-RC0:

    • Feature Model switch to GeoAPI completed with passing CITE tests from GeoServer as sanity check
    • Some major bug fixes related to raster coverage rendering, ArcSDE, and Filter to SQL simplification
    • Build system improvements

    Features from 2.5-M3:

    • OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
    • Usability and Performance improvements to the Feature
    • FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

    Features from 2.5-M2:

    • JAXB bindings for the metadata module (ie support for ISO 19139 documents)
    • FeatureAccess super class for DataStore, allowing data access using ISO

    Features from 2.5-M1:

    • Change over to GeoAPI SimpleFeature
    • Support GetGMLObject
    • Preview of new Swing Widgets (and a warm welcome to Eclesia)

    Features from 2.5-M0:

    • Online User Guide
    • Java 5
    • Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
    • ISO 19107 Geometry implementation available as a supported module
    • DB2 returns to supported status
    • ArcSDE returns to supported status
    • GeometryBuilder utility class
    • A new GPX DataStore

    Release Notes:

    For more information please visit:

    If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

    Enjoy,
    The GeoTools Community

Tell More of the World!

Well that was not very much of the world was it? Lets do freshmeat, sf.net, geotools.org and freegis.

Do it in the Morning

Please don't announce releases on a Friday or weekend. And try to make it in the mornings as well. If it's late then just finish it up the next day. This will ensure that a lot more people will see the announcements.

http://freshmeat.net/projects/geotools/
  1. Add release: http://freshmeat.net/projects/geotools/
  2. Branch: "" (or GT2 for 2.0.x)
  3. Version: Version (example 2.1.M1)
  4. Changes: (Example) 
    (see screen snapshot).

You can also update the screen snapshot to reflect a current geotools application; GeoServer and UDIG have been highlighted in the past. If you are making the release to support a project this is your big chance!

http://sourceforge.net/
  1. Add a news article: http://sourceforge.net/news/submit.php?group_id=4091
  2. Subject: (Make sure it is of the form " released")
  3. Details: allows http links (example)

    The GeoTools 2.5 release is available for download:

    The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is centered around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and will allow the library to evolve into supporting complex data structures.

    GeoTools 2.5 also targets graduation as an OSGeo (The Open Source Geospatial Foundation) project, and includes usability and performance improvements, preview version for the new Swing Widgets, and online and downloadable User Guide, an ISO 19107 Geometry implementation available as a supported module, new GPX DataStore, a much more robust ArcSDE DataStore, and JAXB Bindings for xml marshaling of GeoAPI ISO-19115 metadata structures.

    Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea and Justin who spent some time making the switch to the GeoAPI Feature Model passing GeoServer CITE tests, and to Jody for improving our build system.

    Not to forget, a big thanks to Geomatys, GeoSolutions, Refractions Research, OpenGeo and the community for continuously leveraging the project and making it such a success every day!

    Features from 2.5-RC0:

    • Feature Model switch to GeoAPI completed with passing CITE tests from GeoServer as sanity check
    • Some major bug fixes related to raster coverage rendering, ArcSDE, and Filter to SQL simplification
    • Build system improvements

    Features from 2.5-M3:

    • OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
    • Usability and Performance improvements to the Feature
    • FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

    Features from 2.5-M2:

    • JAXB bindings for the metadata module (ie support for ISO 19139 documents)
    • FeatureAccess super class for DataStore, allowing data access using ISO

    Features from 2.5-M1:

    • Change over to GeoAPI SimpleFeature
    • Support GetGMLObject
    • Preview of new Swing Widgets (and a warm welcome to Eclesia)

    Features from 2.5-M0:

    • Online User Guide
    • Java 5
    • Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
    • ISO 19107 Geometry implementation available as a supported module
    • DB2 returns to supported status
    • ArcSDE returns to supported status
    • GeometryBuilder utility class
    • A new GPX DataStore

    Release Notes:

    For more information please visit:

    If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

    Enjoy,
    The GeoTools Community

The format of the subject is important it gets the message included on the http://sourceforge.net/ Home Page. This is a one shot deal, if you go back and fix any mistakes it is kicked off the Home Page.

http://freegis.org/
  1. Email Jan-Oliver Wagner
  2. To: jan@intevation.de
  3. Subject: Geotools update for FreeGIS site
  4. Text:

    The GeoTools 2.5 release is available for download:

    The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is centered around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and will allow the library to evolve into supporting complex data structures.

    GeoTools 2.5 also targets graduation as an OSGeo (The Open Source Geospatial Foundation) project, and includes usability and performance improvements, preview version for the new Swing Widgets, and online and downloadable User Guide, an ISO 19107 Geometry implementation available as a supported module, new GPX DataStore, a much more robust ArcSDE DataStore, and JAXB Bindings for xml marshaling of GeoAPI ISO-19115 metadata structures.

    Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea and Justin who spent some time making the switch to the GeoAPI Feature Model passing GeoServer CITE tests, and to Jody for improving our build system.

    Not to forget, a big thanks to Geomatys, GeoSolutions, Refractions Research, OpenGeo and the community for continuously leveraging the project and making it such a success every day!

    Features from 2.5-RC0:

    • Feature Model switch to GeoAPI completed with passing CITE tests from GeoServer as sanity check
    • Some major bug fixes related to raster coverage rendering, ArcSDE, and Filter to SQL simplification
    • Build system improvements

    Features from 2.5-M3:

    • OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
    • Usability and Performance improvements to the Feature
    • FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

    Features from 2.5-M2:

    • JAXB bindings for the metadata module (ie support for ISO 19139 documents)
    • FeatureAccess super class for DataStore, allowing data access using ISO

    Features from 2.5-M1:

    • Change over to GeoAPI SimpleFeature
    • Support GetGMLObject
    • Preview of new Swing Widgets (and a warm welcome to Eclesia)

    Features from 2.5-M0:

    • Online User Guide
    • Java 5
    • Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
    • ISO 19107 Geometry implementation available as a supported module
    • DB2 returns to supported status
    • ArcSDE returns to supported status
    • GeometryBuilder utility class
    • A new GPX DataStore

    Release Notes:

    For more information please visit:

    If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

    Enjoy,
    The GeoTools Community

http://java.net/
  1. Submit a news article
  2. Use form at: http://today.java.net/cs/user/create/n
  3. Source: geotools.org
  4. URL: http://geotools.org/
  5. Link to article: http://geotools.org/News
  6. Note Membership required
http://slashgisrs.org/
  1. Submit a news article
  2. Use form at: http://slashgisrs.org/submit.pl (gotta login!)
  3. Use your profile page (example: http://docs.codehaus.org/display/~jive) for Home page
  4. Section: Technology Topic: Open Source Community

    The GeoTools 2.5 release is available for download:

    The GeoTools 2.5 series is reaching stability. The target 2.5.0 release is centered around making a new Feature model available. The new feature model is based on formal GeoAPI interfaces and will allow the library to evolve into supporting complex data structures.

    GeoTools 2.5 also targets graduation as an OSGeo (The Open Source Geospatial Foundation) project, and includes usability and performance improvements, preview version for the new Swing Widgets, and online and downloadable User Guide, an ISO 19107 Geometry implementation available as a supported module, new GPX DataStore, a much more robust ArcSDE DataStore, and JAXB Bindings for xml marshaling of GeoAPI ISO-19115 metadata structures.

    Thanks to everyone who provided feedback on our new Feature model. This release contains several usability improvements based on your feedback; thanks also go out to Andrea and Justin who spent some time making the switch to the GeoAPI Feature Model passing GeoServer CITE tests, and to Jody for improving our build system.

    Not to forget, a big thanks to Geomatys, GeoSolutions, Refractions Research, OpenGeo and the community for continuously leveraging the project and making it such a success every day!

    Features from 2.5-RC0:

    • Feature Model switch to GeoAPI completed with passing CITE tests from GeoServer as sanity check
    • Some major bug fixes related to raster coverage rendering, ArcSDE, and Filter to SQL simplification
    • Build system improvements

    Features from 2.5-M3:

    • OSGeo gradudation! All the headers have changed and we now track license use on a module by module basis
    • Usability and Performance improvements to the Feature
    • FeatureCollection no longer implements SimpleFeature or Collection; removal associated implementation classes such as ResourceCollection

    Features from 2.5-M2:

    • JAXB bindings for the metadata module (ie support for ISO 19139 documents)
    • FeatureAccess super class for DataStore, allowing data access using ISO

    Features from 2.5-M1:

    • Change over to GeoAPI SimpleFeature
    • Support GetGMLObject
    • Preview of new Swing Widgets (and a warm welcome to Eclesia)

    Features from 2.5-M0:

    • Online User Guide
    • Java 5
    • Improved CRSAuthorityFactory implementations available for Java Enterprise Edition users
    • ISO 19107 Geometry implementation available as a supported module
    • DB2 returns to supported status
    • ArcSDE returns to supported status
    • GeometryBuilder utility class
    • A new GPX DataStore

    Release Notes:

    For more information please visit:

    If you are new to GeoTools please consider this release as a good starting point, although the 2.4.x remains the stable branch we have no planned API changes and user documentation available for the 2.5.x series.

    Enjoy,
    The GeoTools Community

    Warning: You may wish to change to HTML Formatted, and insert a few links in!