| [pde-dev] 4.3 Endgame rules for PDE |
The 4.3 endgame plan has been posted:
http://www.eclipse.org/eclipse/development/plans/freeze_plan_4_3.php
Here are the expectations for contributing fixes to PDE during the end game
Documentation changes:
1) Must not require code changes, including setting up context ids
2) Must be tagged with the documentation keyword in bugzilla
3) Changes to general PDE doc (not context help) should belong to PDE Documentation component
4) Should have updated copyright dates on each changed file
May 8-17 - contributions to RC1
To fix a bug:
1) Add RC1 target milestone
2) Push your fix to gerrit or attach a patch (check copyrights for each changed file)
3) Add another committer to the bugzilla review field, add them to the cc list, ask them to review your fix
To review a bug:
1) Check out the fix from Gerrit or apply the patch
2) Verify and approve (+2) on Gerrit or push the changes to master
3) Set the bugzilla review flag to +1
4) Copy the commit url from git.eclipse.org to the bug
5) Assign the bug to the fix creator
6) Mark the bug as RESOLVED FIXED
May 20-24 - contributions to RC2
To fix a bug:
1) Add RC2 target milestone
2) Push your fix to gerrit or attach a patch (check copyrights for each changed file)
3) Add 2 other committers to the bugzilla review field, add them to the cc list, ask them to review your fix
To review a bug:
1) Check out the fix from Gerrit or apply the patch
2a) If you are the first reviewer, verify (+1) on Gerrit
2b) If you are the second reviewer, approve (+2) on gerrit or push the changes to master
3) Set the bugzilla review flag to +1
4) Copy the commit url from git.eclipse.org to the bug
5) Assign the bug to the fix creator
6) Mark the bug as RESOLVED FIXED
May 28-31 - contributions to RC3
RC2 requirements + component lead approval + announcing change to platform-releng-dev@xxxxxxxxxxx + fix creating must verify
June 4-7 - contributions to RC4
RC2 requirements + 2 component leads + announcing change with risk assessment
Thanks,
Curtis