Hi all, We (Shazni, myself and other G-Reg team members) had a chat in the evening today WRT the Repository API/SPI work. We decided to schedule the architecture review of the implementation after having successfully passed the integration tests. The reason being that we may need to revisit the current work based on the success/failure of the test cases and conducting an architecture review until that is done is not going to be productive.
Having said that, we have been able to resolve most of the issues that surfaced when running the registry tests and only a few are pending. Shazni will provide an update on where we stand early next week and we will schedule the required architecture/code reviews soon afterwards. Thanks, Senaka. On Fri, Jan 17, 2014 at 4:56 PM, Sameera Perera <[email protected]> wrote: > We had a sync up today to review the current state of milestone 3, > scheduled for 23rd January. > > Following were the deliverable > s > > o > riginally planned for M3 > > - Carbon Clustering API and Implementation - Phase 02 > - Pluggable Runtime Framework - Phase 02 > - Configuration and Context Model - Phase 03 > - Repository API and Implementation - Phase 03 > > Current status of these deliverables: > > Carbon Clustering API and Implementation > > - Being discussed in archi@ > - Will not be released in M3 > > > Pluggable Runtime Framework > > - Pending review (Scheldued for 2014/1/20) > - Will be ready for M3 > > Configuration and Context model > > - Not started. Will be repriorized (see below) > > Repository API and Implementation > > - The team is running the refactored implementation through existing > registry test cases > - Architecture and code reviews pending > - Further changes to the API may happen > - Will not be ready in M3 > > As the original milestone plan was set out to meet a March deadline and > had some assumptions that were revised at the off site meeting, after 23rd > the team will revise the milestone plan and reprioritize the deliverables > accordingly. This will be used as an opportunity to document the user > stories for C5 features as well as introduce development governance as > discussed with product management this week. > > ------------------------------ > > *Sameera Perera* > Senior Manager, Engineering (Platform TG) > gtalk: [email protected] > Tel : 94 11 214 5345 > Fax :94 11 2145300 > *WSO2, Inc.* <http://wso2.com/> > lean.enterprise.middleware > > > > > > -- > > ------------------------------ > > *Sameera Perera* > Senior Manager, Engineering (Platform TG) > gtalk: [email protected] > Tel : 94 11 214 5345 > Fax :94 11 2145300 > *WSO2, Inc.* <http://wso2.com/> > lean.enterprise.middleware > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com * Member; Apache Software Foundation; http://apache.org <http://apache.org>E-mail: senaka AT wso2.com <http://wso2.com>**P: +1 408 754 7388 <%2B1%20408%20754%207388>; ext: 51736*; *M: +94 77 322 1818 <%2B94%2077%20322%201818> Linked-In: http://linkedin.com/in/senakafernando <http://linkedin.com/in/senakafernando>*Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
