We're now at -rc2 for the October release of OE-Core. I've noticed a sudden surge of patches on the list, several of which are things like version increments which are no longer really appropriate at this point in the release cycle.
Why haven't we branched? The plus side of branching now would be continued patches into master. The downside is that QA and autobuilder resources are concentrating on release and hence not on ensuring regressions are being added. I also really need my energy focused on the release rather than reviewing other code. I'm out of bandwidth so I'm putting off branching. There is also the risk that if we branch, people will continue with master development and ignore the release branch and I'd like to apply a little pressure against this. So if patches are getting ignored its likely they've been deemed not suited to the state of the tree right now. I may start to queue things on master-next but no guarantees and I would ask people to try and help make the release a good one. If there are patches being ignored you think do qualify for -rcX, please ping me as it is hard to keep track of everything. Cheers, Richard _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
