[Releasing] Should we make Qt 5.3.0-1 to fix one Android bug?

[Simon Hausmann]

On Friday 23. May 2014 09.25.32 Turunen Tuukka wrote:
> On 23/05/14 10:40, "Thiago Macieira" <thiago.macieira at intel.com> wrote:
> >Em sex 23 maio 2014, às 07:30:50, Turunen Tuukka escreveu:
> >> We do not know when such new version is released, but it is important to
> >> allow enough time for all Qt users to update their applications in
> >>
> >>various
> >>
> >> stores.
> >> 
> >> Based on the assessment of the fix it does not cause problems to any
> >>
> >>other
> >>
> >> platform, so we should be able to get it in safely.
> >
> >5.3.1 is only a couple of weeks away. Since this seems to crash only on
> >an
> >unreleased OS which is still subject to months of changes, people will
> >have
> >the time to rebuild when the release comes.
> 
> Yes, possibly so. But we do not know exactly when the update is rolled
> out, and there is always risk involved in getting a full patch release
> out. Also, not rushing the patch benefits in being able to accommodate
> more of the user feedback in the coming weeks. It takes some time always
> to move an app into a new version of Qt, get it tested, updated to store,
> users to pull the update etc.
> 
> >I don't think this qualifies as P0.
> 
> Maybe this discussion can be done in the upcoming release team meeting and
> decided there.
> 
> We need to get this fix in anyway to the packages going towards our
> customers, so we might as well update all of the packages.

I think I understand Thiago's hesitation and I'm also doubtful about the real 
impact of this. However if Digia is going to make packages available to the 
commercial customers anyway (due to Digia's priorities), I see little harm in 
updating the Qt project based packages. It sounds like a freebie to me :)


Simon