Community
Participate
Working Groups
We forked org.eclipse.ui.workbench during the 3.6 development cycle. We need a way to ensure that any fixes that went into the bundle after that or will go into that bundle in the future, are also applied to the 4.x copy. For each code change, there are three cases: 1. Hasn't been merged yet. 2. Has been merged successfully. 3. Has been looked at but the change doesn't apply to 4.x. One idea would be to systematically go through every change and add a recognizable code comment to the 3.x stream whenever we did 2. or 3. That way, we could even write a command-line tool that helps us manage this ongoing merge problem. What else could we do?
Not sure if that is an option but switching to git might help.They say with Git merging is a piece of cake but I personally have not seen this in action. Perhaps Alex Blewitt might have an option here, I ask him to comment via Twitter.
See also bug 349177 PW
Aggregate move to M5. Retarget to a different milestone if you wish...
Part of this is now covered in bug 359616. We report commits to common areas that are not propagated between master and R3_development. Most of org.eclipse.ui.workbench is still excluded, though. PW
Works for me.