U-Boot v2019.10-rc4 released
Hey all,
So, I had said I would do -rc4 on September 9th and -rc5 on September 23rd, and now it's the 23rd and I'm doing -rc4. Why? My reminder for -rc4 got lost in the shuffle that day and I didn't remember about it until close to -rc5 time. My fault, oops.
At this point, I'd really like to see pull requests that are fixing bugs or regressions.
I've also today clarified on the
http://www.denx.de/wiki/U-Boot/CustodianGitTrees page that the "next" branch is expected to be rebased. Why? While I'm not sure if I want to apply things directly to the next branch and then give them some sort of automated testing, I do want to try and give changes some sort of build testing and similar sooner than I have, and that was at least a related problem.
In terms of a changelog,
git log --merges v2019.10-rc2..v2019.10-rc3
and again, please make sure to use a tag with a changelog for your pull request or at least a changelog of sorts in the email itself.
The v2019.10 release is currently scheduled for October 7th. Thanks all!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190923/835cdf8f/attachment.sig>
Quoted 10 lines · Tom Rini
Hey all,
So, I had said I would do -rc4 on September 9th and -rc5 on September 23rd, and now it's the 23rd and I'm doing -rc4. Why? My reminder for -rc4 got lost in the shuffle that day and I didn't remember about it until close to -rc5 time. My fault, oops.
At this point, I'd really like to see pull requests that are fixing bugs or regressions.
There is still a pending patch where without it, my board does not boot. Is there any way to integrate this so it can start again?
https://patchwork.ozlabs.org/patch/1143567/
I was really hoping we could get it into the next release. I openly admit I forgot to include the file when i did the SPL conversion to OF_CONFIG.
adam
Quoted 22 lines
I've also today clarified on the
http://www.denx.de/wiki/U-Boot/CustodianGitTrees page that the "next" branch is expected to be rebased. Why? While I'm not sure if I want to apply things directly to the next branch and then give them some sort of automated testing, I do want to try and give changes some sort of build testing and similar sooner than I have, and that was at least a related problem.In terms of a changelog,
git log --merges v2019.10-rc2..v2019.10-rc3
and again, please make sure to use a tag with a changelog for your pull request or at least a changelog of sorts in the email itself.The v2019.10 release is currently scheduled for October 7th. Thanks all!
--
Tom
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
https://lists.denx.de/listinfo/u-boot
Quoted 12 lines · Adam Ford
Quoted 10 lines · Tom Rini
Hey all,
So, I had said I would do -rc4 on September 9th and -rc5 on September 23rd, and now it's the 23rd and I'm doing -rc4. Why? My reminder for -rc4 got lost in the shuffle that day and I didn't remember about it until close to -rc5 time. My fault, oops.
At this point, I'd really like to see pull requests that are fixing bugs or regressions.
Quoted 8 lines
There is still a pending patch where without it, my board does not boot. Is there any way to integrate this so it can start again?
https://patchwork.ozlabs.org/patch/1143567/
I was really hoping we could get it into the next release. I openly admit I forgot to include the file when i did the SPL conversion to
OF_CONFIG.
This sounds like a regression fix so yes, I see no reason it shouldn't come in.
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190923/438e3175/attachment.sig>