[Development] Updating of 3rdparty stuff

Turunen Tuukka tuukka.turunen at theqtcompany.com
Tue Apr 7 16:46:37 CEST 2015


When updating 3rd party modules, it is good to include as reviewer someone from doc team (e.g. Topi Reiniö), someone from release team (e.g. Jani Heikkinen) and Lars as the chief maintainer to approve. In a typical case it is just about updating info in docs what version we have, but in case there are significant changes (e.g. in licensing or functionality) it may need to be considered if we can take the new version. Sometimes there has also been undesired side effects such as performance drop with a new version or a 3rd party module, so it is good to have release team in the loop. But in most cases newer is better also for 3rd party modules :)

Yours,

             Tuukka

________________________________________
Lähettäjä: development-bounces+tuukka.turunen=theqtcompany.com at qt-project.org <development-bounces+tuukka.turunen=theqtcompany.com at qt-project.org> käyttäjän  puolestaThiago Macieira <thiago.macieira at intel.com>
Lähetetty: 7. huhtikuuta 2015 17:29
Vastaanottaja: development at qt-project.org
Aihe: Re: [Development] Updating of 3rdparty stuff

On Tuesday 07 April 2015 11:26:21 Helio Chissini de Castro wrote:
> What we need look for to proceed ?
>
> Or just look  on modules, update, test on the platforms and do a proper
> pull request ?

Right, that should be it. For the libs that are patched, re-apply the patches
too.

Since this is import of 3rdparty code, someone from The Qt Company needs to
approve the change.
--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development


More information about the Development mailing list