Add the release note for 2.8.5 version.
Add the release note for 2.8.4
Add a new bug was fixed in 2.8.3
Add the release node for 2.8.3
Add the release note for the 2.8.2 version.
Add a new completed task.
Add the release note for the 2.8.1
Add the release note for 2.8.0
Add a new feature on the 2.7.2 release note.
Add more notes for 2.7.2 release.
Add the release note for 2.7.2
fixed typos.
Add the release note for 2.7.1
Added the release noe for 2.7.0
update documentation to use 2.6.0 release number.
merge from 2.5 branch
include 2.4.3 release notes from branch
Merge the java 1.6 support node for 2.4.2 release.
update documentation for trunk to use 2.5.0 release number
add support for v2 DataONE API.
merge from branch: more notes on 2.4.1 release in the readme
update to use 2.4.1 so the trunk has all artifacts for upgrades.
add note about archive correction
use v2.4.0 for documentation and upgrade scripts.
merge readme notes from 2.3.1
prep for 2.3.1 release
add more details about 2.3.0 features in the README
use 2.3.0 for this next release of metacat.
make sure all versions are using 2.2.2 of some sort -- thinking of making this release a 2.3.0 release because we will be branching/tagging from the trunk, not the 2.2.x branch.
Added Lauren to contributors list in the metacat guide, and made the two lists match in sort order.
prep project for 2.2.1 patch release -- will also merge to the 2.2.x branch.
prep for 2.2.0 release. include configuration value for metacatui deployment context.
[merge from branch to keep trunk up to date with upgrade history] prep for Metacat 2.1.1 release
merging upgrade scripts from 2.0 branch to trunk. https://redmine.dataone.org/issues/3847
upgrade to Metacat 2.1.0 on the trunk. This includes a new index_event table for storing indexing events that need to be reprocessed. https://projects.ecoinformatics.org/ecoinfo/issues/5944
Use 2.0.7 version number in configuration/upgrade/docs (trunk, even though we will not be releasing 2.0.7 from trunk, we want to have the upgrade scripts included here)
add README note about DOI support http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5513
ready Metacat for 2.0.6 release (docs, db version, build files etc).
additional release notes about archive/delete behavior and HZ upgrade
include note about pathquery performance fix (when using indexed fields)
add note about sanparks/saeon spatial file download: http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5718
shorten the systemmetadata* table names for Oracle's 30 character limit. move version to 2.0.5. http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5717
prep for 2.0.4 release
prep for 2.0.3 release
prep for 2.0.2 release by updating the version numbers.
update for 2.0.1 upgrade -- scripts, docs, readme
clarify release notes for 2.0.0 (minor)
added 2.0.0 targeted bugs to the release notes and fleshed out other major enhancements in the list
no not record EML access rules that use the "denyFirst" permOrder.https://redmine.dataone.org/issues/2614
release notes for 2.0.0
use 2.0.0 -- stub out the release notes
include release notes from 1.9.5 branch (includes v 1.9.3 and 1.9.4)
Merge 1.9.2 changes back into the trunk
Remove redundant Version information
Add 1.9.2 release notes.
Update version to 1.9.1. Add nrs ldap properties to configuration.
reference generic OS installation documentation
point to renamed metacat-install.html
Added 1.9.0 release notes
Checked it into cvs head. Add a note to address the issue of replication.
Check into cvs head. Make a minor change.
Check into cvs head. Change made base on Callie's suggestion.
Checkinto cvs head. Add a paragraph to describe what we will do for illegitimate eml 201 schema.
Added FGDC support to bug fixes listing.
change release number from 1.8 to 1.8.0
added a few bug fixes that were made
added release note about spatial query modification (bug 2972)
Updated change log to include additions for 1.8 release
Change the release number to 1.8
Add release for 1.7.1
Added note to README regarding buildIndex fixes in bug 2469
mention ruby client in readme
updated version number and readme
Added changelog for 1.7.0 to readme file. Updated version number in properties.
updated README with changes for the current day.
Added list of changes which are made for the 1.6 release
Trying a chnage to the README to test CVS commit access.
Updated the lsid support docs and added john,will, and callie tocontributors section of the Readme.
Refactored the build to use a <path> element for the classpath ratherthan ant properties. This makes the classpath easier to manage, but requiredchanges throughout the build. I think everything should still build fine --it works for me.
Upgraded the JDBC driver for postgres to the version 8 driver....
Adding acknowledgement for Mellon support.
Updated README with contributors.
Fixed typos in README, update version for release.
Changes made for release 1.5
Fixed typo.
Fixed some typos in the README, and rearranged a little.
New README in preparation for the 1.4.0 release, and updated the propertiesfile with the new version number.
Revise it a little bit.
New readme file for 1.3.1
Revise readme file for release 1.3
Delete the description about to handle tomcat4. Now it is set as a property in build.xml.
Add note for tomcat 4 to change web.xml
Write the readme for 1.3.0
Change the readme for release 1.2.1
updated README for jing
Update readme for release 1.2.1
Change the describtion for data file path.
changed values for release
Add a note for postgresql user to update table structure.
Add two notes for updating replication table and specifying data file path.
Updated README and build.xml in preparation for a new release. Looks to meas though the dist and distsrc targets are not working properly because thedist target produces a distribution with source code, which it should notdo. Need to check into this.