Releasing Ibator:

1. Increment the version number of Ibator in version.properties

2. Build and test the base Ibator (make sure to use JDK 5.0)

3. Build the new version of the Eclipse feature:
  - Copy new ibator.jar and ibator-src.zip into the core plugin 
  - Increment the version number of the feature
  - Increment the version number of any plugin that has changed
  - Build the doc
  - Add the new version of the feature to site.xml in the IbatorUpdateSite
    project
  - Build the update site (just the new version, not build all)
  - Delete the files artifacts.xml and content.xml generated by the
    site builder (these files do not properly categorize the features.
    See Eclipse bug 227675 for a possible solution in release 3.5)
  - Do SVN Revert on any old plugin versions that were regenerated by the
    site build process

4. Run through the manual test scripts for the Eclipse feature

5. Zip the contents of the update site (remove project metadata)
  
6. Commit everything

7. Make an SVN label

8. Put the new base Ibator zip file in /www/people.apache.org/builds/ibatis/alpha

9. Put the new zipped eclipse site in /www/people.apache.org/builds/ibatis/alpha

10. Update /www/ibatis.apache.org/doc/tools/ibator from SVN (this updates the documentation)

11. Update /www/ibatis.apache.org/tools/ibator from SVN (this updates the Eclipse site)

12. Update the DTD (if required)

13. Update the iBATIS web site

14. Send out the announcement to dev@ and user@