[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [platform-ui-dev] 3.x bugs that might represent e4 requirements?
- From: Boris Bokowski <bokowski@xxxxxxxxx>
- Date: Tue, 22 Sep 2009 12:02:03 -0400
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ZRskLo1WBDPD2+qKp6rAKxV9iLnC63QhzQ4HEGbJL+y0X+T9Wh4cL75lo7XXkAdxwc Oy92tgJFUx7RJ78pBFqqb3yGjdkp8rrMo/pYLL8PSI78YQUlTYEQHi/AxNQUTPpNKONF LZEqfVtx9/hOCpjWxZFeaqRaftIRkG1qU1hIM=
In similar cases, we've been using the "4.0" target milestone to mark
bugs for consideration in 4.0.
On Tue, Sep 22, 2009 at 11:47 AM, Susan Franklin McCourt
> Hi, everyone.
> 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?
>  https://bugs.eclipse.org/bugs/show_bug.cgi?id=289181
> platform-ui-dev mailing list