On Sat, May 16, 2020 at 08:10:04AM +0000, Peng Fan wrote: > Hi Tom, > > > -----Original Message----- > > From: U-Boot <u-boot-boun...@lists.denx.de> On Behalf Of Tom Rini > > Sent: 2020年5月12日 6:29 > > To: u-boot@lists.denx.de > > Cc: u-boot-custodi...@lists.denx.de; > > u-boot-board-maintain...@lists.denx.de > > Subject: [ANN] U-Boot v2020.07-rc2 released > > > > Hey all, > > > > It's release day and I've tagged v2020.07-rc2. At this point out we should > > be > > seeing stabilization, clean-up and localized new features. > > > > Once again, for a changelog, > > git log --merges v2020.07-rc1..v2020.07-rc2 and as always, I ask for more > > details in the PRs people send me so I can put them in the merge commit. > > > > I'm planning to follow the every-other-week RC schedule and release on July > > 6th. I'm also thinking about opening -next again on June 8th as that will > > give > > us a bit more time to focus on stability and regression fixing. > > Will you automatically merge sub-maintainers next tree? Or need > sub-maintainers > to send PR to your next tree? Will your next tree rebase master branch in > time?
So, I forget if I had talked about how I'm running -next for now before or not. I expect to be sent a PR for my -next branch rather than automatically grabbing them from people, and then I take care of merging -next to master after release. -- Tom
signature.asc
Description: PGP signature
