Hi,
From a CI perspective nothing needs to be done.
From the Gerrit side the UI needs to be changed from submit to merge to
staging. Gerrit admins can do that.
The module itself needs to support "make install" and be able to run tests
against the installed version of the module.
By default th
Hi Brett,
> On 13 Jan 2017, at 02:58, Stottlemyer, Brett (B.S.) wrote:
>
> On 12 January 2017 at 08:39, Lars Knoll wrote:
>
>> From the discussion so far I didn't hear too many things that speak against
>> a TP, the code duplication with moc is one of the issues that fall into the
>> 'flagge
> All known blockers should be fixed in these packages and we are
> targeting to release Qt 5.8.0 Tue 17^th January if nothing really
> serious found during testing. So please inform me immediately if there
> is some new blocker in the packages.
QTBUG-56163 is the main blocker for me, which preven
On 12 January 2017 at 08:39, Lars Knoll wrote:
>From the discussion so far I didn't hear too many things that speak against a
>TP, the code duplication with moc is one of the issues that fall into the
>'flagged and need to be resolved before moving out of TP' category for me. How
>about the oth
On 01/11/2017 07:10 PM, Phil Bouchard wrote:
Moreover I will try part of the following kernel level memory manager
sooner or later:
https://github.com/tempesta-tech/tempesta
I just wanted to close the subject with the following note:
I did try the user-space version of the Tempesta Tech memor
> -Original Message-
> From: Development [mailto:development-
> bounces+tuukka.turunen=qt...@qt-project.org] On Behalf Of Stottlemyer,
> Brett (B.S.)
> Sent: torstaina 12. tammikuuta 2017 3.19
> To: development@qt-project.org
> Subject: Re: [Development] Switch Qt Remote Objects to a Tech
On 12 January 2017 at 08:39, Lars Knoll wrote:
> Here are the criteria I think we should have (and that we IMO implicitly used
> in the past):
This smells like something we should be turning into a QUIP.
Eddy.
___
Development mailing list
Devel
> -Original Message-
> From: Mitch Curtis
> I'm noticing this for bugs too (QTBUG-57965). Do you have a report for
> tracking
> this issue, or do you know when it will be fixed?
Done.
I am fixing as soon as somebody points them out to me. There is no easy way to
identify them
--
Al
On tirsdag 10. januar 2017 11.37.56 CET Simon Hausmann wrote:
> (2) I really wish the placement of the configuration files for the
> platforms being moved to qt5.git had a high priority, because it prevents
> situations like these where the R&D organization, the project, contributors
> and part
I'm noticing this for bugs too (QTBUG-57965). Do you have a report for tracking
this issue, or do you know when it will be fixed?
> -Original Message-
> From: Development [mailto:development-bounces+mitch.curtis=qt.io@qt-
> project.org] On Behalf Of Alexander Blasche
> Sent: Monday, 9 Jan
10 matches
Mail list logo
