[U-Boot] [ANN] U-Boot v2016.11 is released
Hey all,
I've released v2016.11 and it's now live on git and FTP and ACD (along with PGP sig file).
In many ways it feels good to say that the highlights of the last release once again apply. We've had more DM conversion work, Kconfig conversion work and arch / SoC / platform updates. We've also had some important filesystem fixes come in and equally as important, test cases added. We also now support the new and default enabled ext4 64bit flag (thanks again Stefan!).
And what I want to highlight here is going forward both relative ease of, and expectations on testing. Last time I talked about test.py and how I'm using it more myself now. This time, I want to talk about travis-ci support. If you use github you can get a more-or-less world build and test.py for all of the QEMU targets we support today done in about 2 and a half hours, wall clock. I don't expect people to do this for iterative development or "trivial" changes, but if you have a series that touches a lot of areas I think it's reasonable to expect that you'll test things out this way. And I'll say now it's not 100%. About once every 10 builds I'll have to go and re-start a sub-job because it will fail to fetch one of the PPAs we use for no apparent reason. But to be clear, it's a few minutes worth of setup and then you push a change and you get build coverage and test coverage. This is really awesome and I wish I had been paying more attention to this sooner.
As always, I know I'm missing pointing out a few things that I should point out and would encourage folks to chime in if there's anything they would like to highlight.
Thanks again everyone!
On Mon, Nov 14, 2016 at 10:16 PM, Tom Rini trini@konsulko.com wrote:
Hey all,
I've released v2016.11 and it's now live on git and FTP and ACD (along with PGP sig file).
In many ways it feels good to say that the highlights of the last release once again apply. We've had more DM conversion work, Kconfig conversion work and arch / SoC / platform updates. We've also had some important filesystem fixes come in and equally as important, test cases added. We also now support the new and default enabled ext4 64bit flag (thanks again Stefan!).
And what I want to highlight here is going forward both relative ease of, and expectations on testing. Last time I talked about test.py and how I'm using it more myself now. This time, I want to talk about travis-ci support. If you use github you can get a more-or-less world build and test.py for all of the QEMU targets we support today done in about 2 and a half hours, wall clock. I don't expect people to do this for iterative development or "trivial" changes, but if you have a series that touches a lot of areas I think it's reasonable to expect that you'll test things out this way. And I'll say now it's not 100%. About once every 10 builds I'll have to go and re-start a sub-job because it will fail to fetch one of the PPAs we use for no apparent reason. But to be clear, it's a few minutes worth of setup and then you push a change and you get build coverage and test coverage. This is really awesome and I wish I had been paying more attention to this sooner.
As always, I know I'm missing pointing out a few things that I should point out and would encourage folks to chime in if there's anything they would like to highlight.
Thanks again everyone!
Unfortunately "Amarula Solutions" is not listed in Employers list [1] for this I sent a domain-map mail to Wolfgang Denk during MW, any edit for this?
[1] http://www.denx.de/wiki/U-Boot/UbootStat_2016_11
Dear Jagan,
In message CAD6G_RTFpFmFWVOtdkeRm_LA1nQgMxtSQSnbToyd_6Y8_icSiw@mail.gmail.com you wrote:
Unfortunately "Amarula Solutions" is not listed in Employers list [1] for this I sent a domain-map mail to Wolfgang Denk during MW, any edit for this?
Where should it show up?
You sent me an entry for a
www.amarulasolutions.com -> Amarula Solutions
mapping, which I did add to the u-boot-config/domain-map used for building this report. AFAICT, there is no single commit log containing "www.amarulasolutions.com".
The git log from v2016.09 through v2016.11 shows author entries for two mail addresses containing anything similar:
jagan@amarulasolutions.com michael@amarulasolutions.com
But neither of them matches "www.amarulasolutions.com", so there are no credits generated.
I was surprised about the "www" part in your domain mapping, but this is what you sent me, so I added it. Please let me know if you think this should be changed.
Best regards,
Wolfgang Denk
Hi Wolfgang Denk,
On Tue, Nov 15, 2016 at 3:45 AM, Wolfgang Denk wd@denx.de wrote:
Dear Jagan,
In message CAD6G_RTFpFmFWVOtdkeRm_LA1nQgMxtSQSnbToyd_6Y8_icSiw@mail.gmail.com you wrote:
Unfortunately "Amarula Solutions" is not listed in Employers list [1] for this I sent a domain-map mail to Wolfgang Denk during MW, any edit for this?
Where should it show up?
You sent me an entry for a
www.amarulasolutions.com -> Amarula Solutionsmapping, which I did add to the u-boot-config/domain-map used for building this report. AFAICT, there is no single commit log containing "www.amarulasolutions.com".
The git log from v2016.09 through v2016.11 shows author entries for two mail addresses containing anything similar:
jagan@amarulasolutions.com michael@amarulasolutions.comBut neither of them matches "www.amarulasolutions.com", so there are no credits generated.
I was surprised about the "www" part in your domain mapping, but this is what you sent me, so I added it. Please let me know if you think this should be changed.
Look like I sent a wrong entry to with "www" part please remove the same.
thanks!
Dear Jagan,
In message CAD6G_RQk=Ra3WL4PpMftxJ+FT4mP6mEs-LDg_c9u3zyqmq8hvQ@mail.gmail.com you wrote:
I was surprised about the "www" part in your domain mapping, but this is what you sent me, so I added it. Please let me know if you think this should be changed.
Look like I sent a wrong entry to with "www" part please remove the same.
Done.
Best regards,
Wolfgang Denk
participants (3)
-
Jagan Teki -
Tom Rini -
Wolfgang Denk