On Sunday, January 27, 2019 11:47:04 AM CET Harri Porten wrote:
> On Sat, 26 Jan 2019, Olivier Goffart wrote:
> > I think the "monorepo" is clearly a good approach. And git is evolving
> > with
> > shadow clones and partial checkout. LLVM/Clang recently choose the
> > monorepo
> > approach as it mo
Hi,
It seems reviewers are mostly happy with the current state of QUIP-13 - the
latest 2 changes where just editorial:
https://codereview.qt-project.org/#/c/246288/
Unless someone still has fundamental objections I'd like to merge this soon. We
can always reiterate on details in follow-up co
Hi,
great to hear :)
wish you luck !
will try the RC-snapshot this evening
ciao
ekke
Am 29.01.19 um 11:32 schrieb Jani Heikkinen:
> Hi,
>
> We have "RC" packages under testing. So far all seems to be pretty much OK so
> if nothing new & serious enough found we should be able to get the releas
Hi,
We have "RC" packages under testing. So far all seems to be pretty much OK so
if nothing new & serious enough found we should be able to get the release out
during this week. Let's keep our fingers crossed.
br,
Jani
btw, there is Qt 5.12.1 "RC" snapshot available via online installer if yo
Am 23.01.19 um 17:03 schrieb Kai Koehne:
>> -Original Message-
>> From: Development On Behalf Of ekke
>> Sent: Wednesday, January 23, 2019 9:45 AM
>> To: development@qt-project.org
>> Subject: Re: [Development] HEADS-UP: Branching from '5.12' to '5.12.1'
>> started
>>
>> seems this time i
>From: Development on behalf of Frederik
>Gladhorn
2 Heads: use the latest revision of each branch (the system we used to have in
the past)
>3 Modules containing pinned dependency sha1s
>Each module is completely self-contained, that means qt5 is not
>required as such (but may still
On fredag 25. januar 2019 21:40:07 CET Thiago Macieira wrote:
> On Friday, 25 January 2019 01:10:35 PST Simon Hausmann wrote:
> > I do quite like what Allan suggested: We could try the cherry-pick the
> > other way around. Volker, Lars, Thiago etc. surely remember the p4i
> > script we used to have
Here are the options we discussed internally. I'm happy to elaborate more in
case something is unclear.
1 Do nothing / today / qt5.git
2 Heads: use the latest revision of each branch (the system we used to have in
the past)
3 Modules containing pinned dependency sha1s
Each module is c
