[U-Boot-Custodians] Merge window and pull requests

Tom Rini trini at konsulko.com
Mon Aug 12 16:31:05 UTC 2019

On Mon, Aug 12, 2019 at 09:07:56AM +0000, Eugen.Hristev at microchip.com wrote:

> Hello Tom,
> Just to clarify the "merge window" policy:
> Do you take PR for new boards after the RC1 tag of a release or we 
> should wait for new boards/features until the next merge window ? 
> (meaning you only take PR with fixes).
> I saw that you are still merging many new things even after RC1 and just 
> before the final release tag.
> I am asking because I want to know whether I should send a PR with new 
> features at any time or have to wait for next release.

So, I'm still trying to get better about what can / can't go in when,
especially with longer release cycles.  To me, self-contained new boards
can come in fairly late, so long as they're self-contained.  So for
example, pulling in a new TI AM335x based board (the SoC is old and well
upstreamed, it's just board / DT files) is fine to bring in if the code
itself is good.  But a brand new SoC and first board isn't
self-contained and should wait.  I'm also trying to make sure I bring in
clean-up series in -rc1 or -rc2 but not later (and those do wait for
-rc2 sometimes, so that they can be reworked to apply again after other
changes went in, in -rc1).  Hope that helps!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot-custodians/attachments/20190812/dcc2be0b/attachment.sig>

More information about the U-Boot-Custodians mailing list