1.7 release feature freeze deadline this Friday

1.7 release feature freeze deadline this Friday

[Richard Purdie]

If you've been in the various calls or read the minutes you'd know about
this but it was mentioned to me that it has not been highlighted on the
mailing list.

The M3 milestone close is the end of the week and this marks the feature
freeze point for the 1.7 release. We do have M4 after this but that is a
bug fixing and stabilisation milestone.

There are some things I may still consider into M4, particular if
they're related to the stated objectives of the release, specifically
the developer workflow enhancements which is running behind schedule. As
time progresses, it will be increasingly unlikely things of that nature
will merge though.

So if there are things you are after to see in 1.7 time is running out,
I at least need to be aware of them ASAP.

Cheers,

Richard

Re: 1.7 release feature freeze deadline this Friday

[Carlos Rafael Giani]

On 08/28/2014 09:16 AM, Richard Purdie wrote:
> If you've been in the various calls or read the minutes you'd know about
> this but it was mentioned to me that it has not been highlighted on the
> mailing list.
>
> The M3 milestone close is the end of the week and this marks the feature
> freeze point for the 1.7 release. We do have M4 after this but that is a
> bug fixing and stabilisation milestone.
>
> There are some things I may still consider into M4, particular if
> they're related to the stated objectives of the release, specifically
> the developer workflow enhancements which is running behind schedule. As
> time progresses, it will be increasingly unlikely things of that nature
> will merge though.
>
> So if there are things you are after to see in 1.7 time is running out,
> I at least need to be aware of them ASAP.
>
> Cheers,
>
> Richard
>

Has the GCC 4.9 situation been solved? At least Chromium was failing to 
build with it. Other packages were affected as well.

Re: 1.7 release feature freeze deadline this Friday

[Richard Purdie]

On Thu, 2014-08-28 at 09:18 +0200, Carlos Rafael Giani wrote:
> On 08/28/2014 09:16 AM, Richard Purdie wrote:
> > If you've been in the various calls or read the minutes you'd know about
> > this but it was mentioned to me that it has not been highlighted on the
> > mailing list.
> >
> > The M3 milestone close is the end of the week and this marks the feature
> > freeze point for the 1.7 release. We do have M4 after this but that is a
> > bug fixing and stabilisation milestone.
> >
> > There are some things I may still consider into M4, particular if
> > they're related to the stated objectives of the release, specifically
> > the developer workflow enhancements which is running behind schedule. As
> > time progresses, it will be increasingly unlikely things of that nature
> > will merge though.
> >
> > So if there are things you are after to see in 1.7 time is running out,
> > I at least need to be aware of them ASAP.
> >
> > Cheers,
> >
> > Richard
> >
> 
> Has the GCC 4.9 situation been solved? At least Chromium was failing to 
> build with it. Other packages were affected as well.

We merged in various gcc updates including a fix for the infamous kernel
bug afaik. I don't know the situation with chromium but that did sound
like a chromium issue rather than gcc...

If we're missing patches to gcc please do shout out but I'm not seeing
bugs which suggest we should default back to 4.8 at this point.

Cheers,

Richard

Re: 1.7 release feature freeze deadline this Friday

[Gary Thomas]

On 2014-08-28 08:23, Richard Purdie wrote:
> On Thu, 2014-08-28 at 09:18 +0200, Carlos Rafael Giani wrote:
>> On 08/28/2014 09:16 AM, Richard Purdie wrote:
>>> If you've been in the various calls or read the minutes you'd know about
>>> this but it was mentioned to me that it has not been highlighted on the
>>> mailing list.
>>>
>>> The M3 milestone close is the end of the week and this marks the feature
>>> freeze point for the 1.7 release. We do have M4 after this but that is a
>>> bug fixing and stabilisation milestone.
>>>
>>> There are some things I may still consider into M4, particular if
>>> they're related to the stated objectives of the release, specifically
>>> the developer workflow enhancements which is running behind schedule. As
>>> time progresses, it will be increasingly unlikely things of that nature
>>> will merge though.
>>>
>>> So if there are things you are after to see in 1.7 time is running out,
>>> I at least need to be aware of them ASAP.
>>>
>>> Cheers,
>>>
>>> Richard
>>>
>>
>> Has the GCC 4.9 situation been solved? At least Chromium was failing to
>> build with it. Other packages were affected as well.
>
> We merged in various gcc updates including a fix for the infamous kernel
> bug afaik. I don't know the situation with chromium but that did sound
> like a chromium issue rather than gcc...
>
> If we're missing patches to gcc please do shout out but I'm not seeing
> bugs which suggest we should default back to 4.8 at this point.

It's not just chromium - midori (at least on ARM) also fails
miserably with 4.9 (I've not tried it with the recent changes)

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------