Re: [LEDE-DEV] 18.06 Status?

2018-05-06 Thread Fernando Frediani
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-06 Thread John Crispin
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-05 Thread Fernando Frediani
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-05 Thread Alberto Bursi
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-05 Thread Fernando Frediani
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-05 Thread John Crispin
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-05 Thread Jaap Buurman
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-01 Thread Eric Luehrsen
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

Re: [LEDE-DEV] 18.06 Status?

2018-05-01 Thread Hannu Nyman
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: [LEDE-DEV] 18.06 Status?

2018-05-01 Thread Jaap Buurman
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