|[platform-ui-dev] 3.x bugs that might represent e4 requirements?|
Do we have a process for identifying platform UI bugs submitted against the 3.x stream that would make good test cases/fixes in the context of e4?
For example, I just responded on a bug  involving the initial size/position of a window, but fixing it would change the widget creation sequence in the JFace window framework. Since there is a workaround, I don't see fixing the bug. However, it's a perfectly reasonable bug and one would hope we would make it go away in e4. It's not something that needs to be considered this early in the design, just something we should have a test case for in the future.
Should we be tagging these kinds of bugs in some way so that as e4 matures we can validate that these bugs are fixed?
Back to the top