I think that the main source tree is in pretty good shape, so branching off the 18.0X rather soon might make sense.

There is alweays the next new exiting feature to be included in, but if the intention is still to make several major releases per year, the next feature will get into the next release rather soon.

So little stuff gets backported to 17.01, that a possible 17.01.5 would be just a quick temporary fix, not a proper solution. jow was talking about that ealier, and a 17.01.5 might be ok as a stopgap or "safe upgrade" from 17.01.x.

If 17.01.5 is really made, at least the mvebu mwlwifi driver should be updated first. 17.01 still has the ancient June 2017 version of mwlwifi driver, while master was recently upgrdaed to 2018-03-30 that is likely the best driver version so far.



Jaap Buurman kirjoitti 1.5.2018 klo 16:44:
Dear all,

If a 18.06 release is still going to require quite a bit of work, I
propose we should look at another 17.01 point release. That should be
a nice stopgap in the form of bug fixes for people that are still
running a stable release. 17.01.4 is getting ancient to be honest.
What do you think?

Yours sincerely,

Jaap Buurman

On Tue, May 1, 2018 at 2:53 PM, Rich Brown <richb.hano...@gmail.com> wrote:
Hi folks,

It has been exactly a month since Hauke sent his note recommending a release 
process for the next OpenWrt stable. 
http://lists.infradead.org/pipermail/lede-dev/2018-April/011704.html I have not 
seen any further discussion of this proposal.

Given that the OpenWrt/LEDE merger was founded on the desire to improve 
communication, I am concerned that we're not talking to each other about 
important questions.

It would be OK if we all agreed that we have too many pieces in flux to talk 
about a stable release. But I don't think it's too soon to talk about pausing 
the project evolution briefly and making the hard decisions about what's in, 
what's out. Then most people (who're unwilling to run a snapshot) can get the 
benefit of all your effort over the last year.

Thanks for listening,

Rich


_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Reply via email to