Well, schedule means a bit of organization and commitment around
something, I personally don't fear it.
I am only putting this point here because something happen the recent
past (including during the merge agreements) that justifies. And again
nothing happens if a feature is skipped.But the m
On 06/05/18 09:43, Jaap Buurman wrote:
Dear John,
That is most excellent to hear :) Please disregard my previous
comment. Where did this decision take place by the way? I tried
searching the mailing list but couldn't find anything. My apologies
for bothering the mailing list with this porpos
They already had jow or someone else sent messages to call for kernel
updates and sending patches before the release, and got stuff done by now.
As per the last answer of John Crispin to this mail thread, they will
release at the beginning of next week.
Developers choose freely what they pref
I didn't mention forcing people at any point. Just having someone to be
in charge in order to organize certain things, get people's availability
and make more thing happen.
With regards schedule the lack of one seems not doing much good, so
having one has the potential to improve things. And a
This isn't a job where you can force people to do anything.
Also, I'm not a fan of half-assing or leaving out things for the sake of
a schedule.
-Alberto
On 05/05/2018 20:41, Fernando Frediani wrote:
One characteristic from OpenWrt, different from other projects is the
lack of a leader or a
One characteristic from OpenWrt, different from other projects is the
lack of a leader or a person who can gather others together, make some
decisions or push for them to happen. If one doesn't like this title it
can also be "Project Manager" or "Project Coordinator". This, in my
view, makes a
On 05/05/18 12:27, Jaap Buurman wrote:
Hi all,
I feel like everybody is just waiting for everybody to agree what
features we want in before coming up with the next step of picking a
date. Obviously this isn't working out very well. Why not turn things
around? Pick a date in a few weeks time on
Hi all,
I feel like everybody is just waiting for everybody to agree what
features we want in before coming up with the next step of picking a
date. Obviously this isn't working out very well. Why not turn things
around? Pick a date in a few weeks time on which the Master branch
will be split to a
On 05/01/2018 10:47 AM, Hannu Nyman wrote:
I think that the main source tree is in pretty good shape, so branching
off the 18.0X rather soon might make sense
I would also think its time to branch 18.[something-soon], and rather
than focus on work that needs yet to be completed, look to cut
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 re
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
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 found
12 matches
Mail list logo
