[Releasing] Testing: 08/29/2012 + linux-g++ (64-bit) [success!]

[lars.knoll at nokia.com]

On Aug 30, 2012, at 1:24 PM, ext Stephen Kelly <stephen.kelly at kdab.com> wrote:

> On Thursday, August 30, 2012 12:08:40 Thiago Macieira wrote:
>> On quinta-feira, 30 de agosto de 2012 11.46.51, Sergio Ahumada wrote:
>>>> Are you frozen on a particular revision? What revision is it? If you're
>>>> not
>>>> going to update the revision, you will need to cherry-pick that patch.
>>>> It
>>>> will cherry-pick cleanly.
>>> 
>>> We should not cherry-pick changes. Packages should be created out of
>>> qt5.git sha1s.
>> 
>> The mksrc.sh script now enforces that. It reads the qt5.git commit and
>> packages exactly the SHA-1s specified there.
> 
> There is already a tag in the qt5.git repo.
> 
> Does that mean that Qt 5.0.0 beta 1 will be completely unusable for windows 
> and mac users using CMake? That's a very bad situation.
> 
>> If someone wants to do a hotfix, they'll need to make a commit in the
>> repository, update qt5.git, commit there too.
> 
> The fix is already in the qtbase repo since 2 days ago.
> 
> Doesn't the update bot automatically update the submodules? Do you mean I 
> should do a manual update of the qtbase sha and submit that?

The process is not fully automatic. The bot creates patches in codereview to update qt5.git, but they need to be approved and staged by a human. I've been doing that over the last 2 weeks to get to the release, but I unfortunately missed this one. The last update probably went in just before your fix.

Lars