[kepler-dev] [Bug 5122] Develop an approval process for patches

[bugzilla-daemon at ecoinformatics.org]

http://bugzilla.ecoinformatics.org/show_bug.cgi?id=5122

Derik Barseghian <barseghian at nceas.ucsb.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |barseghian at nceas.ucsb.edu

--- Comment #1 from Derik Barseghian <barseghian at nceas.ucsb.edu> 2010-08-05 16:21:21 PDT ---
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.

-- 
Configure bugmail: http://bugzilla.ecoinformatics.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.