Bug #5122
open
Develop an approval process for patches
Added by Sean Riddle almost 14 years ago.
Updated over 13 years ago.
Description
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.
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.
Moving this to 2.2 target in case we want to discuss it further then.
What are we doing with respect to this item? Are we going to develop a more formal process?
This is not really a release issue, but it is instead a management issue. Retargeting from 2.2 to unspecified.
Original Bugzilla ID was 5122
Also available in: Atom
PDF