Thanks for testing... and thanks for bringing up bug 428717. I'd say that our options to fix this bug in this week's M2 build are zero, but I wouldn't stop shipping our current M2 because of this bug.
Does it make sense to think about a M2a build as soon as we have a fix ready? That would allow us to get early feedback before M3? Thanks, Markus On Wed, Mar 12, 2014 at 11:50 AM, Ivan Furnadjiev <[email protected]>wrote: > Hi Markus, > this morning I spent couple of hours testing our M2 builds. If we skip the > critical issue with the latest WebKit browsers: > 428717: Invisible Elements in RAP Demo with latest WebKit based browsers > https://bugs.eclipse.org/bugs/show_bug.cgi?id=428717 > everything is looking good. > I want to mention that this bug badly affects Workbench applications based > on Forms, as some of the Forms widgets (Section, ExpandableComposite...) > extend Canvas. There are workarounds mentioned in the bug report. Real fix > will come in the next days. > Best, > Ivan > > > On 3/11/2014 7:31 PM, Markus Knauer wrote: > > Hi RAP Developers, > > this is the candidate build for RAP 2.3.0 M2 (Luna M6) and already > contributed to the Simultaneous Release build: > > RAP Runtime: > p2 repository http://download.eclipse.org/rt/rap/2.3/M2-20140311-0943/ > https://hudson.eclipse.org/rap/view/RAP%20head/job/rap-head-runtime/191/ > > RAP Tools: > p2 repository > http://download.eclipse.org/rt/rap/tools/2.3/M2-20140311-1049/ > https://hudson.eclipse.org/rap/view/RAP%20head/job/rap-head-tools/167/ > > Thanks, > Markus > > > _______________________________________________ > rap-dev mailing > [email protected]https://dev.eclipse.org/mailman/listinfo/rap-dev > > > > _______________________________________________ > rap-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/rap-dev > >
_______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
