On the weekly call Tue 23 January, I proposed that we reduce the scope of the release defining criteria for M7 and delay it's release by 1 week until Feb 5th to allow time to finish off the remaining 'release defining' JIRAs. This proposal was accepted by those on the call and minuted.
The outstanding M7 JIRAs that are marked as 'high' priority were all part of the release defining criteria for M7 and their status is now: WODEN-47 generic extensions methods (deferred) WODEN-54 Interface unit tests (M7) WODEN-55 Binding unit tests (M7) WODEN-56 remove internal classes from extensions pgm model (deferred) WODEN-87 API methods to 'flatten' interface inheritance (M7) WODEN-126 expose xs:schema element via API (M7) The outstanding M7 JIRAs marked as 'low' priority were not part if the M7 release defining criteria and these will now be deferred to the next release. The two deferred high priority JIRAs, WODEN-47 and WODEN-56, cover the programming model changes required for extensions. This is part of a general redesign I want to do of Woden's extensions architecture and I felt this would delay M7 more than 1 week. So as extensions are not actually broken, they just need improving, I proposed we defer these two JIRAs until the release following M7. I will update the Woden website with the new M7 release date and progress indicators on milestone plan. I am still expecting to complete WODEN-87 and WODEN-126 by Monday 29th Jan and then start the release mgt cycle. Graham has partially completed WODEN-54 and is also assigned WODEN-55. regards, John Kaputin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
