On Tue, Oct 08, 2024 at 09:22:50AM +0200, Michal Simek wrote: > Hi Tom, > > On 10/7/24 16:56, Tom Rini wrote: > > Hey all, > > > > It's release day and so here is v2024.07. We had a few last minute bug > > fixes come in, and while I'd prefer they come in earlier in the release > > cycle, I'm still happier people are testing before the release comes out > > instead of after the release is out. 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 v2024.10-rc6..v2024.10 > > contains what I've pulled since the last RC or: > > git log --merges v2024.07..v2024.10 > > 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. v2025.01 is scheduled for Monday, January 6th, 2025 and the > > merge window will close and -rc1 will be released on the 28nd of > > October, and then the next window will open with -rc2, two weeks later. > > I'm also trying something slightly different this release and I've put > > -rc6 in for Monday, December 30th to have one more tag over the end of > > year holidays, to see if that helps with people finding time to test. > > We'll how that went in January. > > Great. Can you please also sync up defconfigs after next merge?
Ah yes, sorry. The downside of the "#include" mechanism is that I have to un-sync that. It's not overly hard to undo, but it means I need to work on the commit rather than just make it part of the release flow. Done now. -- Tom
signature.asc
Description: PGP signature
