Develop an approval process for patches
At present, releasing a patch releases all changes made to the applicable release branch. If not very many people are making patches on any given module, then an ad hoc organizational scheme can be used (Just talk it out) to make sure people aren't stepping on each others toes. This is not always guaranteed to be the case. In the absence of a redesign of the patching system with more than per-module granularity, a social solution has to be developed.
#1 Updated by Derik Barseghian over 9 years ago
To clarify, releasing a patch is a module-level event.
Each minor release will have its own branch in svn, and if two developers are working on the same module in that branch, they need to coordinate with each other, and relevant groups, before releasing the patch. E.g. before a patch in a vanilla Kepler is released, it should be tested and approved by the architecture and leadership teams.