On 6/16/2010 7:34 AM, Thiago Macieira wrote:
More likely than not, in option 2, there would be no patches applied to Qt and
it would be a stock& pristine build. (Note: the current patches are unknown
to us, so this option also implies that they go away unreviewed)
To be understood: yes, we're offering to take ownership of the build. We can
just as well not take on that responsibility -- but in that case, we'll
rebuild Qt for the Nokia MeeGo devices and remove any patches we don't know
about.
Either way, we're setting ourselves up for executing QA on the MeeGo reference
platforms (continuous integration, regression testing, release testing). We
cannot provide the same level of QA or hardening for other devices.
So this is a question to all: what is the preferred method?
well
normally we try to have someone package the software who doesn't have a
vested interest in getting his own upstream deliverable in
(so that the packager can be the checks/balances wrt quality and
stability). We don't have this everywhere, but in practice we sort of do.
Now I'd welcome the Qt team owning the Qt pieces of MeeGo, but there's
actually 3 pieces that are very closely aligned and need to
be owned together: Qt, Qt Mobility and MeeGo Touch Framework.... they
are very much intertwigned in terms of version requirements etc
that right now they need to be owned and updated together. Are you
offering to take on all three?
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
