Hey, John Plocher wrote: > [ 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>
This seems entirely useful to me. We've traditionally tried to push these sorts of changes directly up into the upstream communities first given they have an impact on interfaces, but yes, any change should obviously be characterized by its architectural impact. Hopefully Laca can incorporate this into his review documents. thanks! Glynn
