Release-defining criteria for M7

[John Kaputin <KA...@uk.ibm.com>]

The M7 release is due Jan 29th, which means code freeze around Jan 22nd. We
still have a large number of JIRAs flagged for M7 and limited developer
resources. On the Woden weekly call we discussed the need to define the
release criteria for M7 to allow us to scope down the number of M7 JIRAs if
necessary.

The release-defining criteria we discussed are:
* to pass all of the 'good' document test cases in the W3C WSDL 2.0 suite,
to support the spec's progression from CR to PR
* to implement any required API changes sooner rather than later to
stablize the API
* to implement outstanding unit tests
* to fix major bugs

Excluded from the M7 release-defining criteria are issues like assertion
validation failures, as assertion compliance is not a criteria for the spec
to move to PR and we generally have a lot more work to do on assertion
coverage by Woden and on Woden's validation architecture (validating user
extensions, rule dependency via pre-conditions, etc).

Of the 28 remaining JIRAs currently flagged for the M7 release, I propose
the 16 JIRAs listed below should form our detailed release-defining
criteria (i.e. the "must dos"). Please vote or comment ASAP, as I would
like to update the M7 milestone plan on the Woden website accordingly.

W3C WSDL 2.0 'good' testcase failures:
WODEN-10  SchemaId-1G
WODEN-101 SparqlQuery-1G
WODEN-102 SparqlQuerySimplified-1G

Woden API changes:
WODEN-47  generic collections of extensions as well as/instead of static
typing
WODEN-56  remove need to use *internal* classes when coding extensions
WODEN-87  methods in Interface API to 'flatten' interface inheritance
          (requested for integration of Woden into Axis2)
WODEN-119 readWSDL args should be URI instead of String
WODEN-120 readWSDL methods should return Description not DescriptionElement

Unit tests for Component and Element APIs:
These will test that the implementation supports the Woden API correctly by
testing each method signature in the API. They are not full functional
tests of WSDL 2.0 as this testing is provided by the W3C WSDL 2.0 test
suite. These tests have been outstanding for several milestone releases but
are needed for adequate regression testing.
WODEN-49  tests for ImportElement and IncludeElement (done?)
WODEN-50  tests for Service and Endpoint
WODEN-51  tests for Description and DescriptionElement
WODEN-53  tests for TypesElement, ElementDeclaration, TypeDefinition
WODEN-54  tests for Interface and InterfaceElement and their children
WODEN-55  tests for Binding and BindingElement and their children

Others:
WODEN-45    changes to "ASF Source Header and Copyright Notice Policy"
WODEN-118   NPE when import location does not resolve to a document

regards,
John Kaputin


---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org