5 Super committers are a group of TSC-approved individuals within the
6 OpenDaylight community with the power to merge patches on behalf of projects
7 during approved Release Activities.
10 Super Committer Activities
11 --------------------------
13 Super committers are given super committer powers **ONLY** during TSC-approved
14 activities and are not a power that is active on a regular basis. Once one of
15 the TSC-approved activities are triggered, :doc:`helpdesk <lfdocs:helpdesk>`
16 will enable the permissions listed for the respective activities for the
17 duration of that activity.
24 This activity has been pre-approved by the TSC and does not require a TSC
25 vote. :doc:`Helpdesk <lfdocs:helpdesk>` should be notified to enable the
26 permissions and again to disable the permissions once activities are
29 Super committers are granted powers to merge blocking patches for the duration
30 code of freeze until a release is approved and code freeze is lifted. This
31 permission is only granted for the specific branch that is frozen.
33 The following powers are granted:
35 * Submit button access
37 During this time Super Committers can **ONLY** merge patches that have a +2
38 Code-Review by a project committer approving the merge, and the patch passes
39 Jenkins Verify check. If neither of these conditions are met then **DO NOT**
47 This activity has been pre-approved by the TSC and does not require a TSC
48 vote. :doc:`Helpdesk <lfdocs:helpdesk>` should be notified to enable the
49 permissions and again to disable the permissions once activities are
52 Super committers are granted powers to merge version bump related patches for
53 the duration of version bumping activities.
55 The following powers are granted:
60 * Submit button access
62 These permissions are granted to allow super committers to push through version
63 bump patches with haste. The Remove Reviewer permission is to be used only for
64 removing Jenkins vote caused by a failed distribution-check job, if that
65 failure is caused by a temporary version inconsistency present while the bump
66 activity is being performed.
68 Version bumping activities come in 2 forms.
70 1. Post-release Autorelease version bumping
71 2. MRI project version bumping
73 Case 1, the TSC has approved an official OpenDaylight release and after the
74 binaries are released to the world all Autorelease managed projects are version
75 bumped appropriately to the next development release number.
77 Case 2, During the Release Integrated Deadline of the release schedule MRI
78 projects submit desired version updates. Once approved by the TSC Super
79 Committers can merge these patches across the projects.
81 Ideally the version bumping activities should not include code modifications,
82 if they do +2 Code-Review vote should be complete by a committer on the project
83 to indicate that they approve the code changes.
85 Once version bump patches are merged these permissions are removed.
90 Any activities not in the list above will fall under the exceptional case in
91 which requires TSC approval before Super Committers can merge changes. These
92 cases should be brought up to the TSC for voting.
98 ========================= =================== =================================
100 ========================= =================== =================================
101 Anil Belur abelur abelur@linuxfoundation.org
102 Jamo Luhrsen jamoluhrsen jluhrsen@gmail.com
103 Luis Gomez LuisGomez ecelgp@gmail.com
104 Robert Varga rovarga nite@hq.sk
105 Thanh Ha zxiiro zxiiro@gmail.com
106 ========================= =================== =================================