[LEDE-DEV] Policies for changes to LEDE stable branches, or LEDE patches in general?

[Bjørn Mork]

Hello,

I note that a recent commit to the lede-17.01 branch has added a few
driver patches which have barely hit the mainline kernel:

https://github.com/lede-project/source/commit/1ab41265c39354332630bcba0ec704abd2e790f0

This surprised me quite a bit.  I would expect any such fixes to go the
normal route from mainline to stable to LEDE, like they do for most
other current distros. This usually does not take more than a couple of
weeks anyway, and less if a fix is critical.

It was surprising enough that this hit the master branch.  But going
into a stable LEDE branch before davem has considered it for stable
kernels?  Why?

And then there is the issue of making LEDE patches for fixes which can
be, or already are, upstream: Is that wise use of resources? Reading
https://lede-project.org/docs/guide-developer/the-source-code I see that
I am wrong thinking that there are policies for this.

But maybe there should be?



Bjørn