[ Referring to the "JDS code review process" discussion at
http://www.opensolaris.org/jive/thread.jspa?threadID=14977 ]
Someplace in this process there needs to be a (quick and simple) determination
of architectural impact to ensure that new features or changes that impact
others get the exposure and review that they need. Something like:
If (impact limited to JDS) then
<follow this process>
else if (impacts other parts of OpenSolaris) then
<need to engage with the ARC community>
else /* ? impacts upstream suppliers (GNOME, Mozilla...) ? */
<need to engage with supplier community>
See
"What sort of changes need ARC approval?"
http://www.opensolaris.org/os/community/arc/arc-faq/arc-project-size/
and
"When should changes to the architecture of the system be reviewed?"
http://www.opensolaris.org/os/community/arc/arc-faq/arc-lifecycle/
-John
This message posted from opensolaris.org
