Re: Switch to AT-SPI/CORBA as the default for GNOME 2.30

[Willie Walker <walker willie gmail com>]

Hi Matthias:

We've yet to be able to get a successful run of the Orca regression test suite when running with AT-SPI/D-Bus.  In addition, we're seeing non-deterministic behavior when running on different machines.  Some of these may be race conditions, as I tend to see problems when running on my slow NetBook that I didn't see when running on a faster machine.  This behavior can manifest itself in performance problems, reentrancy problems, etc.  These bugs do not seem unsurmountable, but they will take time and we suspect more exist.  The reentrancy issues in particular are quite elusive and difficult to pin down.

To the point that funding permits, we will still continue to develop AT-SPI/D-Bus even if AT-SPI/CORBA is the default.

Will

On Feb 4, 2010, at 1:50 PM, Matthias Clasen wrote:

> On Thu, Feb 4, 2010 at 1:44 PM, Willie Walker <walker willie gmail com> wrote:
>> Hi All:
>> 
>> We've spent the past couple days debugging AT-SPI/D-Bus issues.  While we were able to uncover and fix a number of bugs, Mark and I chatted today and agreed that the responsible thing to do would be to go back to AT-SPI/CORBA as the default for 2.30.
>> 
>> With 2.29.90 coming up next week, it seems as though we should do this sooner than later.  I can make all the changes necessary to make the default builds of all the AT-SPI/CORBA related stuff put things in the default location and the default builds of all the AT-SPI/D-Bus related stuff relocate things.  With this, we will be back at the same spot we were with GNOME 2.28.x, but with the ability for people to ship/install/activate AT-SPI/D-Bus.
>> 
>> Are you all OK with this?
>> 
> 
> Can you give us an overview over the problem areas that make you
> consider At-spi/DBus to be less stable than At-spi/Corba ?
> 
> If we are going back / staying with Corba now, is there a plan or
> roadmap for getting things worked out in time for 2.31 ?