[U-Boot] [ANN] U-Boot v2019.10-rc3 released
Hey all,
It's release day and here's v2019.10-rc3. We're well into what should be the stabilization period at this point. Going forward I am hoping for PRs that are bug fixes / regression fixes, Kconfig migrations or very self contained new boards and similar. If you have a series is "big" but doesn't quite fit into that list, please let me know with a patchwork link to the series in reply here. I'd like to get a handle on how much stuff like that it outstanding so that I can get an idea on what I should try and do about a "next" branch more often than I have and what rules might apply to it.
In terms of a changelog, git log --merges v2019.10-rc2..v2019.10-rc3 continues to look 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 still planning on doing -rc4 on September 9th and -rc5 on September 23rd with the release scheduled on October 7th. Thanks all!
Hi Tom,
Subject: [U-Boot] [ANN] U-Boot v2019.10-rc3 released
Hey all,
It's release day and here's v2019.10-rc3. We're well into what should be the stabilization period at this point. Going forward I am hoping for PRs that are bug fixes / regression fixes, Kconfig migrations or very self contained new boards and similar. If you have a series is "big" but doesn't quite fit into that list, please let me know with a patchwork link to the series in reply here. I'd like to get a handle on how much stuff like that it outstanding so that I can get an idea on what I should try and do about a "next" branch more often than I have and what rules might apply to it.
The i.MX8MM patch set. hope that could be queued into next tree. https://patchwork.ozlabs.org/cover/1153589/
Should that go through Stefano's tree into your next branch or you could pick up if the patch set is good?
Thanks, Peng.
In terms of a changelog, git log --merges v2019.10-rc2..v2019.10-rc3 continues to look 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 still planning on doing -rc4 on September 9th and -rc5 on September 23rd with the release scheduled on October 7th. Thanks all!
-- Tom
On Tue, Aug 27, 2019 at 07:20:07AM +0000, Peng Fan wrote:
Hi Tom,
Subject: [U-Boot] [ANN] U-Boot v2019.10-rc3 released
Hey all,
It's release day and here's v2019.10-rc3. We're well into what should be the stabilization period at this point. Going forward I am hoping for PRs that are bug fixes / regression fixes, Kconfig migrations or very self contained new boards and similar. If you have a series is "big" but doesn't quite fit into that list, please let me know with a patchwork link to the series in reply here. I'd like to get a handle on how much stuff like that it outstanding so that I can get an idea on what I should try and do about a "next" branch more often than I have and what rules might apply to it.
The i.MX8MM patch set. hope that could be queued into next tree. https://patchwork.ozlabs.org/cover/1153589/
Should that go through Stefano's tree into your next branch or you could pick up if the patch set is good?
I would expect i.MX8MM to go through Stefano's tree as it's "imx". That said, I also expect if http://www.denx.de/wiki/U-Boot/CustodianGitTrees had more than one sentence about "next" branches or http://www.denx.de/wiki/U-Boot/DevelopmentProcess mentioned them at all and I said what I was doing in the main tree, others might follow suit as their own time permits.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Tom,
On 27/08/2019 02:19, Tom Rini wrote:
Hey all,
It's release day and here's v2019.10-rc3. We're well into what should be the stabilization period at this point. Going forward I am hoping for PRs that are bug fixes / regression fixes, Kconfig migrations or very self contained new boards and similar. If you have a series is "big" but doesn't quite fit into that list, please let me know with a patchwork link to the series in reply here. I'd like to get a handle on how much stuff like that it outstanding so that I can get an idea on what I should try and do about a "next" branch more often than I have and what rules might apply to it.
In terms of a changelog, git log --merges v2019.10-rc2..v2019.10-rc3 continues to look 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 still planning on doing -rc4 on September 9th and -rc5 on September 23rd with the release scheduled on October 7th. Thanks all!
I wasn't able to find a -rc4 tag in the git log. Did you postpone the publication of v2019.10-rc4?
Regards, Matthias
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de https://lists.denx.de/listinfo/u-boot
On Wed, Sep 18, 2019 at 04:23:35PM +0200, Matthias Brugger wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Tom,
On 27/08/2019 02:19, Tom Rini wrote:
Hey all,
It's release day and here's v2019.10-rc3. We're well into what should be the stabilization period at this point. Going forward I am hoping for PRs that are bug fixes / regression fixes, Kconfig migrations or very self contained new boards and similar. If you have a series is "big" but doesn't quite fit into that list, please let me know with a patchwork link to the series in reply here. I'd like to get a handle on how much stuff like that it outstanding so that I can get an idea on what I should try and do about a "next" branch more often than I have and what rules might apply to it.
In terms of a changelog, git log --merges v2019.10-rc2..v2019.10-rc3 continues to look 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 still planning on doing -rc4 on September 9th and -rc5 on September 23rd with the release scheduled on October 7th. Thanks all!
I wasn't able to find a -rc4 tag in the git log. Did you postpone the publication of v2019.10-rc4?
Ah, so, thanks for bringing it up. I did indeed fail to tag -rc4 on schedule (missed my reminder) and didn't recall it until this past Monday. Things have been generally quiet, but there are a few fixes I do need to grab, and I'm just going to do -rc4 on the 23rd at this point.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 18/09/2019 16:25, Tom Rini wrote:
On Wed, Sep 18, 2019 at 04:23:35PM +0200, Matthias Brugger wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Hi Tom,
On 27/08/2019 02:19, Tom Rini wrote:
Hey all,
It's release day and here's v2019.10-rc3. We're well into what should be the stabilization period at this point. Going forward I am hoping for PRs that are bug fixes / regression fixes, Kconfig migrations or very self contained new boards and similar. If you have a series is "big" but doesn't quite fit into that list, please let me know with a patchwork link to the series in reply here. I'd like to get a handle on how much stuff like that it outstanding so that I can get an idea on what I should try and do about a "next" branch more often than I have and what rules might apply to it.
In terms of a changelog, git log --merges v2019.10-rc2..v2019.10-rc3 continues to look 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 still planning on doing -rc4 on September 9th and -rc5 on September 23rd with the release scheduled on October 7th. Thanks all!
I wasn't able to find a -rc4 tag in the git log. Did you postpone the publication of v2019.10-rc4?
Ah, so, thanks for bringing it up. I did indeed fail to tag -rc4 on schedule (missed my reminder) and didn't recall it until this past Monday. Things have been generally quiet, but there are a few fixes I do need to grab, and I'm just going to do -rc4 on the 23rd at this point.
Perfect, thanks for the update :)
participants (3)
-
Matthias Brugger -
Peng Fan -
Tom Rini