[Development] Qt 4.8: disabling the CI and closing for anything except security fixes
jake.petroules at petroules.com
Fri Aug 14 11:13:36 CEST 2015
> On Aug 13, 2015, at 11:50 PM, Knoll Lars <Lars.Knoll at theqtcompany.com> wrote:
> On 14/08/15 08:25, "Sarajärvi Tony" <tony.sarajarvi at theqtcompany.com <mailto:tony.sarajarvi at theqtcompany.com>>
>>> -----Original Message-----
>>> From: development-bounces+tony.sarajarvi=theqtcompany.com at qt-
>>> project.org [mailto:development-
>>> bounces+tony.sarajarvi=theqtcompany.com at qt-project.org] On Behalf Of
>>> Thiago Macieira
>>> Sent: 14. elokuuta 2015 3:40
>>> To: development at qt-project.org
>>> Subject: [Development] Qt 4.8: disabling the CI and closing for anything
>>> except security fixes
>>> I recently tried to fix a very simple bug in Qt 4.8 but I can't get the
>>> to integrate because the CI seems to have fallen into disrepair.
>>> Instead of using valuable QA time in fixing the CI for 4.8, I'd like to
>>> instead that we simply disable the CI for that version and close Qt 4.8
>>> any submission except security fixes. Gerrit would be configured for
>>> merging instead of staging, but that would only be enabled to Gerrit
>>> and they'd only do it after confirmation from the security team
>>> (security at qt-
>>> Any objections?
>> Not from me ;)
> Agreed. This sounds like the best way to continue.
> Development mailing list
> Development at qt-project.org <mailto:Development at qt-project.org>
> http://lists.qt-project.org/mailman/listinfo/development <http://lists.qt-project.org/mailman/listinfo/development>
+1, Qt 4.8 needs to die. :)
However, I've submitted a patch which would resolve the CI issue in question (https://codereview.qt-project.org/#/c/123073/). Do we want to push that through along with some of the currently posted patches before the lockdown happens?
Jake Petroules - jake.petroules at petroules.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Development