[U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips
Wolfgang Denk
wd at denx.de
Sat Apr 25 12:48:23 CEST 2009
Dear David Brownell,
In message <200904250105.41050.david-b at pacbell.net> you wrote:
>
> Yes. The issue is needing to guess what's up ... so for
> example, I seem to observe that "merge window closed" must
> not be the same as "first RC is out", which isn't how the
> Linux process works. But that's the only example I've
> seen for how the new u-boot cycles should work...
Maybe I pout a little more meaning in the words "release candiate".
After the end of a merge window, there is usually still a long
backlog of patches that has not been merged, and after that there are
several rounds of debugging / bug fixing needed. IMO it makes little
sense to call anything in this state a "release candiate".
That's why we still have no "rc" in the current release cycle.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"I've finally learned what `upward compatible' means. It means we get
to keep all our old mistakes." - Dennie van Tassel
More information about the U-Boot
mailing list