________________________________________
> Lähettäjä: Development 
> <development-bounces+tuukka.turunen=theqtcompany....@qt-project.org> 
> käyttäjän  puolestaHeikkinen Jani <jani.heikki...@theqtcompany.com>
> Lähetetty: 12. huhtikuuta 2016 9:46
> Vastaanottaja: Thiago Macieira; development@qt-project.org
> Aihe: Re: [Development] CI for Qt WebKit
>
>>>That's exactly the time that they should be in the way... We may break those
>>>modules temporarily, but not leave them broken at the time of the release.
>
>
> I disagree. If module is removed (obsolete in .gitmodules) that cannot delay 
> the release: It is just insane. if there is some reason(s) for that then I 
> think we shouldn't even remove the module at all. 
> That 
> kind of semi-removal is the worst case: We are playing it is removed but 
> actually working like it is officially as a part of release/packages. It is 
> confusing for us all and causes just this kind of unnecessary 
> hassle :(
>
> br,
> jani

+1

Exactly like Jani said, when some module is removed it does not matter for the 
release. 

If there is any issue with a released version of Qt, that can be fixed also 
after the release if someone needs to use such a removed module with that 
release of Qt.

Yours,

                   Tuukka
________________________________________
Lähettäjä: Development 
<development-bounces+jani.heikkinen=theqtcompany....@qt-project.org> käyttäjän  
puolestaThiago Macieira <thiago.macie...@intel.com>
Lähetetty: 12. huhtikuuta 2016 1:20
Vastaanottaja: development@qt-project.org
Aihe: Re: [Development] CI for Qt WebKit

On segunda-feira, 11 de abril de 2016 20:34:44 PDT Knoll Lars wrote:
> The reason is that they should not be in the way to getting our releases
> out.

That's exactly the time that they should be in the way... We may break those
modules temporarily, but not leave them broken at the time of the release.

--
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

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

Reply via email to