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

[bugzilla-daemon at ecoinformatics.org]

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

           Summary: Develop an approval process for patches
           Product: Kepler
           Version: 2.0.0
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P2
         Component: build system
        AssignedTo: david.v.welker at gmail.com
        ReportedBy: swriddle at gmail.com
         QAContact: kepler-dev at kepler-project.org
   Estimated Hours: 0.0


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.

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