On 09/19/2017 04:15 AM, Marek Vasut wrote:
On 09/18/2017 06:06 PM, Tom Rini wrote:
On Mon, Sep 18, 2017 at 04:51:31PM +0100, Burton, Ross wrote:
On 18 September 2017 at 16:46, Otavio Salvador < otavio.salvador@ossystems.com.br> wrote:
What is the policy on doing u-boot version upgrades this late in the
release cycle? SHouldn't this wait until after the release?
Why?
It is just another recipe and we are upgrading to the final release.
As Martin said, it was already broken.
I'll take the responsibility to fix it. But as other packages, upgrades has risk and we have more than enough time to proper fix it.
Why? Because it was merged to master after the freeze.
Personally I'm of the opinion that u-boot is one of those special recipes that if an upgrade appears just after freeze, we consider it. If we don't keep it up to date BSPs won't use the recipe, and we'll be back to every BSP layer containing its own special copy of the u-boot recipe.
Also please note that U-Boot has a rather regular and public release schedule: http://www.denx.de/wiki/U-Boot/ReleaseCycle so you can have a good idea beforehand if you want to grab something for a release or not.
Personally, I would like to see this in. But the security issue that's been disclosed now is "resolved" just by not enabling functionality that no one was enabling in mainline, and will be removed in the next release, so don't feel you need to pull it in on those grounds.
I agree that the 2017.09 upgrade is a good idea.
OK, I just wanted to make sure everyone was on the same page about timing of the update. We certainly don't want very many recipes to decide they are special and take version bumps right up to release.
Philip