[ANN] U-Boot v2023.07 released
Hey all,
It's a week after our planned release date, but, we've gotten the issues that had delayed the release sorted out and understood. I want to thank everyone that's contributed to this release, not just in terms of code, but documentation, testing and otherwise ensuring things go as smoothly as they can.
In terms of a changelog, git log --merges v2023.07-rc6..v2023.07 contains what I've pulled since the last RC or: git log --merges v2023.04..v2023.07 for changes since the last full release. As always, more details in pull requests (or the tags referenced by them) will result in more details here.
The merge window is formally open again, and I'll be merging in next shortly. v2023.10 is scheduled for October 2nd, 2023 and the merge window will close and -rc1 will be released on the 24th of July, and then the next window will open with -rc2, two weeks later. I know this means the merge window is slightly shorter than normal but with the next window having been open, I think that's fine.
Thanks all!
On Mon, Jul 10, 2023 at 02:14:58PM -0400, Tom Rini wrote:
Hey all,
It's a week after our planned release date, but, we've gotten the issues that had delayed the release sorted out and understood. I want to thank everyone that's contributed to this release, not just in terms of code, but documentation, testing and otherwise ensuring things go as smoothly as they can.
In terms of a changelog, git log --merges v2023.07-rc6..v2023.07 contains what I've pulled since the last RC or: git log --merges v2023.04..v2023.07 for changes since the last full release. As always, more details in pull requests (or the tags referenced by them) will result in more details here.
The merge window is formally open again, and I'll be merging in next shortly. v2023.10 is scheduled for October 2nd, 2023 and the merge window will close and -rc1 will be released on the 24th of July, and then the next window will open with -rc2, two weeks later. I know this means the merge window is slightly shorter than normal but with the next window having been open, I think that's fine.
And I forgot to update the Makefile to drop -rc6. As I've also merged next to master and pushed that out, re-doing the tag seems sub-optimal. If it's important to distribution folks I can make v2023.07.01 which will really _just_ be correcting the Makefile. Or I'm open to other suggestions.
On 7/11/23 02:47, Tom Rini wrote:
On Mon, Jul 10, 2023 at 02:14:58PM -0400, Tom Rini wrote:
Hey all,
It's a week after our planned release date, but, we've gotten the issues that had delayed the release sorted out and understood. I want to thank everyone that's contributed to this release, not just in terms of code, but documentation, testing and otherwise ensuring things go as smoothly as they can.
In terms of a changelog, git log --merges v2023.07-rc6..v2023.07 contains what I've pulled since the last RC or: git log --merges v2023.04..v2023.07 for changes since the last full release. As always, more details in pull requests (or the tags referenced by them) will result in more details here.
The merge window is formally open again, and I'll be merging in next shortly. v2023.10 is scheduled for October 2nd, 2023 and the merge window will close and -rc1 will be released on the 24th of July, and then the next window will open with -rc2, two weeks later. I know this means the merge window is slightly shorter than normal but with the next window having been open, I think that's fine.
And I forgot to update the Makefile to drop -rc6. As I've also merged next to master and pushed that out, re-doing the tag seems sub-optimal. If it's important to distribution folks I can make v2023.07.01 which will really _just_ be correcting the Makefile. Or I'm open to other suggestions.
Linus did this in past but on RC version. https://lwn.net/Articles/848265/
I think you can rename incorrect tag first and remove origin one.
And creating new tag (with -rc6 removed from Makefile) make sense to me.
Thanks, Michal
On Mon, Jul 10, 2023 at 08:47:53PM -0400, Tom Rini wrote:
On Mon, Jul 10, 2023 at 02:14:58PM -0400, Tom Rini wrote:
Hey all,
It's a week after our planned release date, but, we've gotten the issues that had delayed the release sorted out and understood. I want to thank everyone that's contributed to this release, not just in terms of code, but documentation, testing and otherwise ensuring things go as smoothly as they can.
In terms of a changelog, git log --merges v2023.07-rc6..v2023.07 contains what I've pulled since the last RC or: git log --merges v2023.04..v2023.07 for changes since the last full release. As always, more details in pull requests (or the tags referenced by them) will result in more details here.
The merge window is formally open again, and I'll be merging in next shortly. v2023.10 is scheduled for October 2nd, 2023 and the merge window will close and -rc1 will be released on the 24th of July, and then the next window will open with -rc2, two weeks later. I know this means the merge window is slightly shorter than normal but with the next window having been open, I think that's fine.
And I forgot to update the Makefile to drop -rc6. As I've also merged next to master and pushed that out, re-doing the tag seems sub-optimal. If it's important to distribution folks I can make v2023.07.01 which will really _just_ be correcting the Makefile. Or I'm open to other suggestions.
OK, I've tagged and pushed v2023.07.01 which is only fixing the Makefile so that it reports v2023.07.01. I'll push a small change to master so that we're not oon v2023.07-rc6 until we move to v2023.10-rc1 shortly.
On Tue, Jul 11, 2023 at 09:55:21AM -0400, Tom Rini wrote:
On Mon, Jul 10, 2023 at 08:47:53PM -0400, Tom Rini wrote:
On Mon, Jul 10, 2023 at 02:14:58PM -0400, Tom Rini wrote:
Hey all,
It's a week after our planned release date, but, we've gotten the issues that had delayed the release sorted out and understood. I want to thank everyone that's contributed to this release, not just in terms of code, but documentation, testing and otherwise ensuring things go as smoothly as they can.
In terms of a changelog, git log --merges v2023.07-rc6..v2023.07 contains what I've pulled since the last RC or: git log --merges v2023.04..v2023.07 for changes since the last full release. As always, more details in pull requests (or the tags referenced by them) will result in more details here.
The merge window is formally open again, and I'll be merging in next shortly. v2023.10 is scheduled for October 2nd, 2023 and the merge window will close and -rc1 will be released on the 24th of July, and then the next window will open with -rc2, two weeks later. I know this means the merge window is slightly shorter than normal but with the next window having been open, I think that's fine.
And I forgot to update the Makefile to drop -rc6. As I've also merged next to master and pushed that out, re-doing the tag seems sub-optimal. If it's important to distribution folks I can make v2023.07.01 which will really _just_ be correcting the Makefile. Or I'm open to other suggestions.
OK, I've tagged and pushed v2023.07.01 which is only fixing the Makefile so that it reports v2023.07.01. I'll push a small change to master so that we're not oon v2023.07-rc6 until we move to v2023.10-rc1 shortly.
And it's been pointed out I got that one wrong, so I've moved it to -dont-use and I'll really, properly, make a v2023.07.02 later today. Sorry for the confusion.
On Tue, Jul 11, 2023 at 10:55:40AM -0400, Tom Rini wrote:
On Tue, Jul 11, 2023 at 09:55:21AM -0400, Tom Rini wrote:
On Mon, Jul 10, 2023 at 08:47:53PM -0400, Tom Rini wrote:
On Mon, Jul 10, 2023 at 02:14:58PM -0400, Tom Rini wrote:
Hey all,
It's a week after our planned release date, but, we've gotten the issues that had delayed the release sorted out and understood. I want to thank everyone that's contributed to this release, not just in terms of code, but documentation, testing and otherwise ensuring things go as smoothly as they can.
In terms of a changelog, git log --merges v2023.07-rc6..v2023.07 contains what I've pulled since the last RC or: git log --merges v2023.04..v2023.07 for changes since the last full release. As always, more details in pull requests (or the tags referenced by them) will result in more details here.
The merge window is formally open again, and I'll be merging in next shortly. v2023.10 is scheduled for October 2nd, 2023 and the merge window will close and -rc1 will be released on the 24th of July, and then the next window will open with -rc2, two weeks later. I know this means the merge window is slightly shorter than normal but with the next window having been open, I think that's fine.
And I forgot to update the Makefile to drop -rc6. As I've also merged next to master and pushed that out, re-doing the tag seems sub-optimal. If it's important to distribution folks I can make v2023.07.01 which will really _just_ be correcting the Makefile. Or I'm open to other suggestions.
OK, I've tagged and pushed v2023.07.01 which is only fixing the Makefile so that it reports v2023.07.01. I'll push a small change to master so that we're not oon v2023.07-rc6 until we move to v2023.10-rc1 shortly.
And it's been pointed out I got that one wrong, so I've moved it to -dont-use and I'll really, properly, make a v2023.07.02 later today. Sorry for the confusion.
OK, and, sigh, really, v2023.07.02 is there. And I re-checked before pushing that it's just fixing the version number. So this is what people should use for distributions.
Hi,
Btw. Githubs dependa-bot reports some security related issues with pythons setup-tools. As far as i see it should only affects tests...as i don't use the tests i cannot say if it breaks anything and so not send a patch in ML.
maybe this can be done directly in original uboot repo.
https://github.com/frank-w/u-boot/pull/6
I hope this way of reporting is ok :) regards Frank
On Tue, Jul 11, 2023 at 06:54:42PM +0200, Frank Wunderlich wrote:
Hi,
Btw. Githubs dependa-bot reports some security related issues with pythons setup-tools. As far as i see it should only affects tests...as i don't use the tests i cannot say if it breaks anything and so not send a patch in ML.
maybe this can be done directly in original uboot repo.
https://github.com/frank-w/u-boot/pull/6
I hope this way of reporting is ok :)
Yes, thanks for bringing this up. This has been addressed in next (and now master) with: commit b1574ddebd34fee83e4c11f9da54b52ba7198fa8 Author: Tom Rini trini@konsulko.com Date: Tue May 30 15:50:30 2023 -0400
python: Update requirements.txt for security issues
Per GitHub Dependabot: - Use setuptools 65.5.1 to avoid some DoS issue - Use requests 2.31.0 to avoid leaking some proxy information
Signed-off-by: Tom Rini trini@konsulko.com Tested-by: Heinrich Schuchardt xypron.glpk@gmx.de
But wasn't merged for the release as the issues themselves are overall not something U-Boot hits but rather just parts of the frameworks we use for testing and doc generation.
participants (3)
-
Frank Wunderlich -
Michal Simek -
Tom Rini