Task #891
Story #980: Document process for product release cycle
schema change procedure
100%
Description
Updating schemas is a fragile, ad-hoc process. To get it right, one has to ensure all of the tags in the xsd are described correctly in the documentation, and reflected in the dataone-service-api service types (Java classes). these classes are not directly created, but generated using binding.xml files. Finally, the schemas themselves need to be properly versioned (svn tagged). All members of the core development team should be able to readily make necessary changes, but the complexity for making the changes correctly is high.
A procedure is needed to make this process repeatable and less frustrating, and error-prone.
Related issues
History
#1 Updated by Rob Nahf over 14 years ago
- Target version deleted (
CCI-0.6) - Milestone set to CCI-0.6
#2 Updated by Rob Nahf over 14 years ago
- Position set to 32
#3 Updated by Dave Vieglais over 14 years ago
- Position set to 3
- Target version set to Sprint-2010.41
- Position deleted (
32)
#4 Updated by Dave Vieglais over 14 years ago
- Start date set to 2010-10-07
- Parent task set to #980
- Tracker changed from Story to Task
#5 Updated by Dave Vieglais about 14 years ago
- Status changed from New to In Progress
#6 Updated by Dave Vieglais about 14 years ago
- Status changed from In Progress to Closed
Documented at:
https://repository.dataone.org/documents/Projects/cicore/development/build/html/software_versioning.html
Basically - create a release of the common types schema, then do not change it until dependencies have been updated to support that revision of the schema.