On Mon, Jan 17, 2011 at 06:29:06AM +0800, Sam Spilsbury wrote:
> On Mon, Jan 17, 2011 at 3:44 AM, Kristian Lyngstol
> <[email protected]> wrote:
> > I had expected the glib-work to be merged with mainline by now.  This is a
> > prerequisite for the a11y-work, since we'd otherwise have to do it using
> > the glib-plugin as the test-base, which I'd rather avoid. Specially since
> > I'm not the one doing the actual glib/atk stuff, I'm only pitching in to
> > set up interfaces and mentor Ale a bit.
> 
> It wasn't ready yet. It changes a lot of how core works and I want to
> get it signed off by some of the other key players here. There are
> still bugs because it conflicts with the gconf backend for
> libcompizconfig in quite a nasty way.

Understandable. Is there any chance it'll create sensible pull queues,
though? It'll be hard to review it if it's 6-months worth of work. I've
looked at the code and played with it, mind you, and I wasn't really able
to generate sensible patch sets - it simply grew too big for conventional
patch/merge review.

> > The lack of merging is holding up involvement due to the "waiting for the
> > next great thing!"-phenomenon...
> 
> The code has always been available -
> git://git.compiz.org/git/users/dbo/compiz-with-glib-mainloop. Just
> because it hasn't been merged yet, it doesn't mean that we all agree
> that core is going to go in this direction, I just don't want to merge
> it yet since there are bugs that need to be worked out.

I don't think there's any real chance that it wont be pulled in, unless
it's prolonged (ie: nomad/object framework/etc). Don't you think it would
be easier for everyone to pitch in if we only had one code-base to focus
on? It's not my place to push this agenda further, so "just sayin'".

> In the meantime I believe the glib plugin should be sufficient to
> provide enough of a glib mainloop to do ATK with. We only needed glib
> dispatching integrated in core for unity since there was the issue of
> timeout accuracy.

Ok, understandable. I'll go ahead with the glib-plugin. Hopefully it'll
re-kindle my interest enough to help out so we can get the glib-branch
merged.

> > So my question becomes: what's the merge plan?
> 
> Soon.
> 
> I'm currently inundated with fixing bugs and I really haven't had the
> chance to go through the full steps to merge this branch.

Excellent.

Just for the record: I'll take massive instability in master over prolonged
used of two different branches. It's much more inspiring.

- Kristian

Attachment: signature.asc
Description: Digital signature

_______________________________________________
dev mailing list
[email protected]
http://lists.compiz.org/mailman/listinfo/dev

Reply via email to