[U-Boot] U-Boot ARM merge strategy, was: there are non-DM6446 DaVinci chips
Jerry Van Baren
gerald.vanbaren at ge.com
Mon Apr 27 15:44:15 CEST 2009
Wolfgang Denk wrote:
> 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
Make sense on "rc" not really being a release candidate. How about
tagging "mc" for "Merge Closed"?
gvb
More information about the U-Boot
mailing list