From trini at konsulko.com Mon Jan 9 17:08:19 2023 From: trini at konsulko.com (Tom Rini) Date: Mon, 9 Jan 2023 11:08:19 -0500 Subject: [ANN] U-Boot v2023.01 released Message-ID: <20230109160819.GQ3787616@bill-the-cat> Hey all, It's release day and so here's v2023.01. I want to note now that once I merge in the next branch, there'll have been some pretty big changes merged in, mainly that CONFIG -> Kconfig migration will finally be largely done (there's some corner case symbols I'm tracking down next, but they weren't enabled normally anyhow). So please test your platforms out to ensure that nothing was inadvertantly broken. And if you see a DM migration warning printed while building, lets get the migration done, or speak up as to what's holding things back. In terms of a changelog, git log --merges v2023.01-rc4..v2023.01 contains what I've pulled since the last RC or: git log --merges v2022.10..v2023.01 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. And now the merge window continues to be open and I'll merge next in to master shortly. v2023.04 is scheduled for release on Monday, April 4th 2023 and the merge window closes on January 30th. On that note, I want to try something a bit different moving forward. I'm going to open the -next branch when I release -rc2, and by that point changes for master need to be fairly clearly in the "fixes something" category. If it's a new feature or platform that's late, it can go to -next, which will be open and I'll be encouraging people to look at and test. Why? The biggest issue we ran in to with this release has been changes that came in late and had unintended side effects. I should have taken them to next instead, honestly. So this is how we address the problem moving forward I think, being stricter about changes to master and by also having a schedule on when next will be open and an expectation to use it. Thanks all! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: From trini at konsulko.com Mon Jan 9 20:01:30 2023 From: trini at konsulko.com (Tom Rini) Date: Mon, 9 Jan 2023 14:01:30 -0500 Subject: [ANN] U-Boot v2023.01 released In-Reply-To: <20230109160819.GQ3787616@bill-the-cat> References: <20230109160819.GQ3787616@bill-the-cat> Message-ID: <20230109190130.GE3787616@bill-the-cat> On Mon, Jan 09, 2023 at 11:08:19AM -0500, Tom Rini wrote: > Hey all, > > It's release day and so here's v2023.01. I want to note now that once I > merge in the next branch, there'll have been some pretty big changes > merged in, mainly that CONFIG -> Kconfig migration will finally be > largely done (there's some corner case symbols I'm tracking down next, > but they weren't enabled normally anyhow). So please test your platforms > out to ensure that nothing was inadvertantly broken. And if you see a DM > migration warning printed while building, lets get the migration done, > or speak up as to what's holding things back. > > In terms of a changelog, > git log --merges v2023.01-rc4..v2023.01 > contains what I've pulled since the last RC or: > git log --merges v2022.10..v2023.01 > 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. > > And now the merge window continues to be open and I'll merge next in to > master shortly. v2023.04 is scheduled for release on Monday, April 4th > 2023 and the merge window closes on January 30th. > > On that note, I want to try something a bit different moving forward. > I'm going to open the -next branch when I release -rc2, and by that > point changes for master need to be fairly clearly in the "fixes > something" category. If it's a new feature or platform that's late, it > can go to -next, which will be open and I'll be encouraging people to > look at and test. Why? The biggest issue we ran in to with this release > has been changes that came in late and had unintended side effects. I > should have taken them to next instead, honestly. So this is how we > address the problem moving forward I think, being stricter about changes > to master and by also having a schedule on when next will be open and an > expectation to use it. I've merged and pushed next to master. And due to the finalization (with caveats, sigh) of CONFIG -> Kconfig or CFG, if you have an outstanding new platform patch, it's best if you can rebase and repost it rather than having the custodian make an attempt at it. Thanks! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: From trini at konsulko.com Mon Jan 30 22:05:27 2023 From: trini at konsulko.com (Tom Rini) Date: Mon, 30 Jan 2023 16:05:27 -0500 Subject: [ANN] U-Boot v2023.04-rc1 released Message-ID: Hey all, So, I've gotten back on regular schedule and here is -rc1, on time. I've picked up a Rockchip revert, which should fix some problems but I suspect will break some other platforms. I look forward to Kever having a chance to address the issue and get everything working for the full release. I've gone over my queue, and I think it's in OK shape, without anything too big that needs to come in still, and has been around long enough to do so. There's some older series that I do need to provide some feedback on. And, I want to emphasize something I've mentioned in a few places. I'm going to be happy taking big PRs still, for -rc2. But at -rc2 I'm going to open -next, and everything else needs to go to -next if it's not fixing bugs. This means there's a number of platforms I'm needing a PR for. So I will be sending out some off-list messages to check in with people, and I know there's a few possible problems here so I might still have to make an exception, but I think in general this will help us all overall. In terms of a changelog, git log --merges v2023.01..v2023.04-rc1 contains what I've pulled but as always, better PR messages and tags will provide better results here. I'm going to try and stay on schedule now and that means the rest of the rcs every other Monday, and with final release on April 3rd, 2023. Thanks all! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: not available URL: From kever.yang at rock-chips.com Tue Jan 31 04:00:52 2023 From: kever.yang at rock-chips.com (Kever Yang) Date: Tue, 31 Jan 2023 11:00:52 +0800 Subject: [ANN] U-Boot v2023.04-rc1 released In-Reply-To: References: Message-ID: <3d4be9ee-4b1e-67f4-0fc6-20bde829b729@rock-chips.com> Hi Tom, On 2023/1/31 05:05, Tom Rini wrote: > Hey all, > > So, I've gotten back on regular schedule and here is -rc1, on time. I've > picked up a Rockchip revert, which should fix some problems but I > suspect will break some other platforms. I look forward to Kever having > a chance to address the issue and get everything working for the full > release. It's the binman support case without TPL on rockchip platform, will fix later. Thanks, - Kever > I've gone over my queue, and I think it's in OK shape, without > anything too big that needs to come in still, and has been around long > enough to do so. There's some older series that I do need to provide > some feedback on. > > And, I want to emphasize something I've mentioned in a few places. I'm > going to be happy taking big PRs still, for -rc2. But at -rc2 I'm going > to open -next, and everything else needs to go to -next if it's not > fixing bugs. This means there's a number of platforms I'm needing a PR > for. So I will be sending out some off-list messages to check in with > people, and I know there's a few possible problems here so I might still > have to make an exception, but I think in general this will help us all > overall. > > In terms of a changelog, > git log --merges v2023.01..v2023.04-rc1 > contains what I've pulled but as always, better PR messages and tags > will provide better results here. > > I'm going to try and stay on schedule now and that means the rest of the > rcs every other Monday, and with final release on April 3rd, 2023. > Thanks all! >