[Releasing] Meeting minutes: Qt release team meeting 12.01.2016

[Jason H]

> On 13/01/16 11:44, "Releasing on behalf of Heikkinen Jani" <releasing-bounces at qt-project.org on behalf of jani.heikkinen at theqtcompany.com> wrote:
> 
> >Meeting minutes from Qt Release Team meeting 12th January 2016
> >
> >
> >Qt 5.6 status:
> >- QTQAINFRA-943 should be now fixed but fixes aren't in qt5.git yet
> >    * Update 13th Jan: qt5.git integration succeed,
> >fixes for QTQAINFRA-943 in. Unfortunately
> >changes waiting for it aren't in yet
> >--> branching cannot start yet. Hoping we get missing changes in during this week and we so on can start branching at the begining of next week.
> >- RC blocker
> > list here: 
> >https://bugreports.qt.io/issues/?filter=17225 <https://bugreports.qt.io/issues/?filter=17225>
> >
> >
> >
> >Qt 5.7 status:
> >- No progress with QNX/std::atomic related issues
> >--> Cannot start FF/Branching yet, hoping we can progress with those during next week
> >
> >
> >Qt 4.8 & bugreports.qt.io:
> >- Qt 4.8 branch has been closed for a while (except security fixes) and support has ended
> >- bugreports.qt.io has some 1500+ bugs reported \ open \ in progress against Qt 4.8.x versions
> >- Agreed to close those Qt 4.8 and older bugs with proper message
> >   
> >* ' 'please re-open if still valid in Qt 5' or something similar
> >
> >


If I were to come up with code for OSX/iOS Multimedia recording backend configuration by tommorow, it would not be in the 5.7 release?