From trini at konsulko.com Wed May 15 19:59:52 2019 From: trini at konsulko.com (Tom Rini) Date: Wed, 15 May 2019 15:59:52 -0400 Subject: [U-Boot-Board-Maintainers] [ANN] U-Boot v2019.07-rc2 released Message-ID: <20190515195952.GM22232@bill-the-cat> Hey all, It's 2 days past release day, oops, and here is v2019.07-rc2. I think we're largely in good shape, but there's some big things to address still. Things that we need to address are what to do about the code that has gone past the DM migration. What I've said elsewhere is that I want to disable building of the code for a release, and remove it in a following release. How close are we to being able to do that? Well, Jagan started out a series for SPI that did most of what I wanted but didn't stop building the code. I've taken that and reworked it so we don't build the code in question, but do build the platforms. The only thing right now preventing me from posting it, aside from one last world build (which is in progress) is that it really will make a lot of PowerPC platforms build-but-useless. I don't think there's a good option to pick from here but I am hopeful we'll see at least a few platforms updated and converted after this happens. In terms of a changelog, git log --merges v2019.07-rc1..v2019.07-rc2 looks pretty good but the content there varies based on what was given to me in the PR. So please, the more details in the request the better! I'm planning on doing -rc3 on the 27th of May with -rc4 on June 10th and -rc5 on June 24th with the release scheduled on July 8th. Thanks all! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From trini at konsulko.com Mon May 27 18:35:43 2019 From: trini at konsulko.com (Tom Rini) Date: Mon, 27 May 2019 14:35:43 -0400 Subject: [U-Boot-Board-Maintainers] [ANN] U-Boot v2019.07-rc3 released Message-ID: <20190527183543.GG20781@bill-the-cat> Hey all, It's release day and here is v2019.07-rc3. I think I have a few outstanding regression fixes to pull in still, and then of course Kconfig migrations. So, what are we doing about DM migration deadlines? Well, first, let me say again, that DM is not required for SPL. This comes up enough that I want to say it again here. Next, if there is active progress on converting things, we'll keep from pulling the code out. This is why for example, we haven't yet pulled out a lot of deprecated SPI code. Some of it is still in progress on being converted, so I need to update the series I posted after the last -rc to remove still less drivers. In terms of a changelog, git log --merges v2019.07-rc2..v2019.07-rc3 continues to improve in quality. If you're sending me a PR, please include a few lines or words in summary and I'll be sure to put it into the merge commit. As this cycle is coming closer to an end, I feel it's time to ask. Is anyone out there being more frustrated with a 3 month release cycle than with a 2 month cycle? I feel like the answer is that the 3 month cycle is working better than 2 and we should keep that going. I'm planning on doing -rc4 on June 10th and -rc5 on June 24th with the release scheduled on July 8th. Thanks all! -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From sr at denx.de Tue May 28 05:06:03 2019 From: sr at denx.de (Stefan Roese) Date: Tue, 28 May 2019 07:06:03 +0200 Subject: [U-Boot-Board-Maintainers] [U-Boot] [ANN] U-Boot v2019.07-rc3 released In-Reply-To: <20190527183543.GG20781@bill-the-cat> References: <20190527183543.GG20781@bill-the-cat> Message-ID: <874a79f2-03a9-abb1-cd34-5f6e6fe1418e@denx.de> Hi Tom, On 27.05.19 20:35, Tom Rini wrote: > It's release day and here is v2019.07-rc3. I think I have a few > outstanding regression fixes to pull in still, and then of course > Kconfig migrations. > > So, what are we doing about DM migration deadlines? Well, first, let me > say again, that DM is not required for SPL. This comes up enough that I > want to say it again here. Next, if there is active progress on > converting things, we'll keep from pulling the code out. This is why > for example, we haven't yet pulled out a lot of deprecated SPI code. > Some of it is still in progress on being converted, so I need to update > the series I posted after the last -rc to remove still less drivers. > > In terms of a changelog, > git log --merges v2019.07-rc2..v2019.07-rc3 > continues to improve in quality. If you're sending me a PR, please > include a few lines or words in summary and I'll be sure to put it into > the merge commit. > > As this cycle is coming closer to an end, I feel it's time to ask. Is > anyone out there being more frustrated with a 3 month release cycle than > with a 2 month cycle? I feel like the answer is that the 3 month cycle > is working better than 2 and we should keep that going. I personally favor the 2 months release cycle. My main (mostly practical) reason being here, that I don't have to queue non-fixes patches that long and can push them upstream more frequently / sooner. But I can also live with the 3 month release cycle, so if the majority prefers this, then lets stick with it. Thanks, Stefan