Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[eclipse.org-architecture-council] [Bug 330312] New: Rules for project patches in the train 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=330312 
Product/Component: Community / Architecture Council

           Summary: Rules for project patches in the train
    Classification: Eclipse Foundation
           Product: Community
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: major
          Priority: P3
         Component: Architecture Council
        AssignedTo: eclipse.org-architecture-council@xxxxxxxxxxx
        ReportedBy: gunnar@xxxxxxxxxxxxxxx
                CC: wayne@xxxxxxxxxxx


With the addition of Object Teams to the train there is now a patched version
of JDT Core available in the repository. AFAIK it's the first time this
happens.

We need to discuss how we should handle this. I propose something similar to
the API rules for the train. 

(A) We need documentation which explicitly explain what has been patched. This
should be Bugzillas with the patches attached.

(B) We need Bugzillas opened against the patched project in order to discuss
the necessary API/extensibility changes in order to get rid of the patch.

(C) The patched project must respond to (B) within a reasonable time with a
proposed road-map towards implementing the necessary changes.

(D) The patch producers must work together with the patched project in order to
implement the necessary changes.

(E) If the changes can't be implemented in time an approval must be requested
from the AC. The AC will review and discuss the changes in detail.

-- 
Configure bugmail: https://bugs.eclipse.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Back to the top