Folks, $subject is something we need to do to ensure that whatever we have discussed during the previous reviews have been implemented. For code reviews, we have the Crucible projects, so the sessions leads please go through those and provide status updates by the end of this week. When it comes to architecture reviews, we only have the notes that are sent after the reviews. IMO, that is a bit harder to manage & track. I think we should use Crucible for architecture reviews as well. I will check on how that can be done. In the meantime, we need to go through the old architecture review notes & check what has been incorporated & what hasn't. Srinath, what is the best way to do that?
-- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **[email protected]* <[email protected]>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
