g
[mailto:development-bounces+jani.heikkinen=digia@qt-project.org] On Behalf
Of Heikkinen Jani
Sent: 10. huhtikuuta 2014 9:06
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: Re: [Development] HEADS UP: Qt 5.3.0 - merge stable into release
Importance: High
Hi all,
As
en=digia@qt-project.org
[mailto:development-bounces+jani.heikkinen=digia@qt-project.org] On Behalf
Of Heikkinen Jani
Sent: 10. huhtikuuta 2014 9:06
To: development@qt-project.org
Cc: releas...@qt-project.org
Subject: Re: [Development] HEADS UP: Qt 5.3.0 - merge stable into release
Import
Hi all,
As informed last week merge from stable to release will happen today. Stable is
now closed and so on no new changes aren't allowed to be staged in. We will
wait until existing integrations are finished (either succeed or failed) and
start merge after that. We will inform when merge is d
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> [...]
> As per Qt Commit Policy #11, fixes should be "submit[ted] against the lowest
> applicable branch from which a release is still planned."
>
> That's what I've been doing here. Or are you saying
t@qt-project.org; releas...@qt-project.org
>>Subject: Re: [Development] HEADS UP: Qt 5.3.0 - merge stable into release
>>
>>On Tuesday 08 April 2014 07:44:30 Heikkinen Jani wrote:
>>> >>I would also like to request that the following be merged into release
>&
On Tuesday 08 April 2014 07:44:30 Heikkinen Jani wrote:
> >>I would also like to request that the following be merged into release
> >>
> >>*before* it becomes 5.3:
> >> https://codereview.qt-project.org/79787
> >> https://codereview.qt-project.org/79827
> >>
> >>They're both simple documentati
Em ter 08 abr 2014, às 06:10:00, Sergio Ahumada escreveu:
> No changes can be merged in qtbase#release at this point without
> cherry-picking some test fixes first, so they need to be re-targeted to
> stable
I cherry-picked the test.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software
-project.org
Cc: releas...@qt-project.org
Subject: Re: [Development] HEADS UP: Qt 5.3.0 - merge stable into release
>>I would also like to request that the following be merged into release
>>*before* it becomes 5.3:
>>
>> https://codereview.qt-project.org/79787
>> htt
>>I would also like to request that the following be merged into release
>>*before* it becomes 5.3:
>>
>> https://codereview.qt-project.org/79787
>> https://codereview.qt-project.org/79827
>>
>>They're both simple documentation fixes, and already approved.
In my opinion these changes should be
On Thursday 03 April 2014 11:44:20 Giuseppe D'Angelo wrote:
> Given that we're post-beta, can we do the header diff review before that
> date?
I've done some review on new classes. Some is already in, these are still
pending:
QPageSize; API: must go in before release:
https://codereview.qt-pro
On 3 April 2014 09:42, Heikkinen Jani wrote:
> We are about to start the "Qt 5.3.0" release as agreed in [1], which means
> that:
>
>
>
> - We plan to do a fast-forward merge from 'stable' into 'release' branch
>
> on April 10th.
Given that we're post-beta, can we do the header diff review before
Hi,
On 03/04/14 09:53, "Sergio Ahumada" wrote:
>On 03.04.2014 09:42, Heikkinen Jani wrote:
>> Hi,
>>
>> We are about to start the "Qt 5.3.0" release as agreed in [1], which
>> means that:
>>
>> - We plan to do a fast-forward merge from 'stable' into 'release' branch
>> on April 10th.
>
>Hi,
>
On 03.04.2014 09:42, Heikkinen Jani wrote:
> Hi,
>
> We are about to start the "Qt 5.3.0" release as agreed in [1], which
> means that:
>
> - We plan to do a fast-forward merge from 'stable' into 'release' branch
> on April 10th.
Hi,
I think I got lost somewhere. I thought we were going to create
Hi,
We are about to start the "Qt 5.3.0" release as agreed in [1], which means that:
- We plan to do a fast-forward merge from 'stable' into 'release' branch
on April 10th.
- After April 10th any changes that are required for 5.3.0 needs to be
pushed to the 'release' branch. So if your changes a
14 matches
Mail list logo
