having a release every 2-3 years when APs have a life of ~18 months means that
nobody is ever going to be able to run a release on something they can buy in
the store.
even releases every year is too slow.
Other than not releasing as frequently, and not updating to current kernels,
what other things do you think the Devs should not be doing?
and what do you think about the items that the LEDE Devs said were a problem?
David Lang
On Thu, 30 Jun 2016, Tom Psyborg wrote:
Looks like a common problem is when devs get paid well, they are coming up
with more and more problems, ideas to solve these and waste too much time
on unnecessary things.
If you only used the time invested in organizing of all these meet-ups to
commit all the patches sent to mailing list that were not applied due to
various reasons (from my example they were created manually using diff) it
would make the project more easier to handle and easier to focus on
important things.
You have Chaos Calmer stable release that is not really that stable, trunk
on kernel 4.xx containing many bugs, bunch of hardware that is not fully
supported yet etc.
Instead of forcing "stable" releases every year you should have kept the
old way of development, even if it took 2-3 years to accomplish that, but
then provide support and updates for this stable release during next few
years.
Forcing endless kernel updates leaves no room for detailed testing, not to
mention usage of the built firmware and from my perspective this makes the
overall project lose it's popularity which results in less discovered bugs,
sent and especially committed patches, people active on dev board and more
spam.
On 29 June 2016 at 23:23, Felix Fietkau <n...@nbd.name> wrote:
On 2016-06-29 17:02, Jo-Philipp Wich wrote:
Hi Imre,
can you provide a summary of the discussion?
Imre's mail is pretty much a summary of the discussion that we had.
We got along nicely and decided that to really resolve our issues we do
need a proper face to face meeting.
IRC/E-Mail just doesn't have the necessary bandwidth for it, and I'm not
sure if Google Hangout is a solution either.
- Felix
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
