Em Terça-feira 19 Outubro 2010, às 18:04:05, [email protected] escreveu:
> > This is a bit unfortunate for us since we do need to focus on XInput 2.1
> > anyway: other teams will not stop because of MeeGo. If they forge ahead
> > with the development, we need to be a part of it to ensure our needs are
> > met.
> 
> Yes - I agree. It is unfortunate but many times the upstream schedules
> don't match with distro's.

Of course. I mean, even Qt's schedule doesn't match MeeGo's right now. This is 
something we want to address in Qt in a future release and bring our release 
cycle in sync with MeeGo.

I just thought that X.org had a fairly stable 6-month schedule which we used. 
From what I understand from Ubuntu, their 6-month cycles are timed so that 
X.org's release happens, the next month there's a GNOME release, then the one 
after Ubuntu releases. And that's in April and October.

> > One final question: if the X.org input driver is written with XI2.1 and
> > works on top of X.org 1.9, can we still add it to MeeGo 1.2?
> 
> From my POV yes but it is really a question to the X team if they are
> willing to support and maintain that setup. And I am not the only one who
> needs to say it is okay.

Hence this email to the mailing list :-)

> > Note that I have no idea if this driver is possible on top of X.org 1.9.
> > But before I ask anyone to commit resources to this backport, it's
> > important to know if it can be accepted. That is, if it comes at the
> > correct time, with the usual quality reviews. I just need to know that
> > this option isn't outright rejected.
> 
> Please ask. 

Ok, I will. As soon as I know, I'll post here too.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to