Re: [E-devel] What are we going to release?

2017-12-19 Thread William L. Thomson Jr.
On Wed, 20 Dec 2017 09:53:05 +1030 Simon Lees wrote: > > > Both mostly dual. Well there goes my only assumption as to why one system has issues and not another. I guess maybe hardware. Some things like screenshot I would not think involved hardware drivers. I guess it could.

Re: [E-devel] What are we going to release?

2017-12-19 Thread Simon Lees
On 20/12/17 09:05, William L. Thomson Jr. wrote: > On Wed, 20 Dec 2017 08:22:49 +1030 > Simon Lees wrote: > >> On 20/12/17 05:39, William L. Thomson Jr. wrote: >>> On Mon, 18 Dec 2017 17:43:29 + >> >>> I completely disagree! EFL is a total mess! IMHO what needs to be >>>

Re: [E-devel] What are we going to release?

2017-12-19 Thread William L. Thomson Jr.
On Wed, 20 Dec 2017 08:22:49 +1030 Simon Lees wrote: > On 20/12/17 05:39, William L. Thomson Jr. wrote: > > On Mon, 18 Dec 2017 17:43:29 + > > > I completely disagree! EFL is a total mess! IMHO what needs to be > > done is EO and Wayland should be EFL 2.x. 1.x should remain

Re: [E-devel] What are we going to release?

2017-12-19 Thread Simon Lees
On 20/12/17 05:39, William L. Thomson Jr. wrote: > On Mon, 18 Dec 2017 17:43:29 + > Stephen Houston wrote: > >> I really think a consensus needs to be reached here. The uncertainty >> has too many ill effects in other areas of the project, not the least >> of which

Re: [E-devel] What are we going to release?

2017-12-19 Thread William L. Thomson Jr.
On Mon, 18 Dec 2017 17:43:29 + Stephen Houston wrote: > I really think a consensus needs to be reached here. The uncertainty > has too many ill effects in other areas of the project, not the least > of which is documentation as Andy has said, as well as a difficulty >

Re: [E-devel] What are we going to release?

2017-12-18 Thread Jean-Philippe André
therwise. otherwise this is not a discussion. > > > > > > > > > > > > > However if the plan you described is publicly available then I > > > > apologise > > > > > > > for the confusion. I can point these individuals to the > document > > and >

Re: [E-devel] What are we going to release?

2017-12-18 Thread Stephen Houston
; > > a...@andywilliams.me> > > > > > > > said: > > > > > > > > > > > > > > > This has become a circular argument, as many do around here, > vis: > > > > > > > > *) people are asking for us to try an

Re: [E-devel] What are we going to release?

2017-12-11 Thread Carsten Haitzler
people where are asking for a release of a small susbet of > > the > > > > api? > > > > > > show > > > > > > me. > > > > > > > > > > > > > I cannot believe that all of the new APIs are completely unstable >

Re: [E-devel] What are we going to release?

2017-12-10 Thread Jean-Philippe André
On Mon, Dec 11, 2017 at 3:36 PM, Simon Lees wrote: > On 11/12/17 14:41, Jean-Philippe André wrote: > > Cedric mentioned to me a couple of times how long it took large projects > > using Qt4 to finally move on to Qt5. So we're trying to avoid that > > bottleneck. > > I don't think

Re: [E-devel] What are we going to release?

2017-12-10 Thread Simon Lees
On 11/12/17 14:41, Jean-Philippe André wrote: > Cedric mentioned to me a couple of times how long it took large projects > using Qt4 to finally move on to Qt5. So we're trying to avoid that > bottleneck. I don't think for most large projects it wasn't that long for Qt4-Qt5, the API changes were

Re: [E-devel] What are we going to release?

2017-12-10 Thread Jean-Philippe André
nterfaces > > > > > agreed on. you have to make your case for that CHANGE. don't tell > me > > > > > "people > > > > > are asking". show me the emails here asking, and from who. show me > the > > > irc > > > > >

Re: [E-devel] What are we going to release?

2017-12-10 Thread Carsten Haitzler
orking on eo/interfaces can ALL come to a > > consensus... > > > > nothing is going to change. and there is no input from most of them at > > this > > > > point, and no overwhelming evidence to ignore any input from them if it > > > > were

Re: [E-devel] What are we going to release?

2017-12-10 Thread Andrew Williams
and no overwhelming evidence to ignore any input from them if it > > > were to > > > come. > > > > > > > If we cannot make any release in the way previously discussed then we > > > > absolutely should have some other way of illustrating our confidence >

Re: [E-devel] What are we going to release?

2017-12-10 Thread Carsten Haitzler
nd those > > > marked as BETA are the classes we feel could be eliciting feedback. > > > This way we are able to show where we know we have not tested as much and > > > can show a journey through creation, testing and integration into the > > BETA > > > ar

Re: [E-devel] What are we going to release?

2017-12-10 Thread Andrew Williams
ion into the > BETA > > area. > > > > Without this we are just hoping that some day all our classes will be > > stable so we can roll a release... > > > > Andrew > > On Sat, 9 Dec 2017 at 12:48, Carsten Haitzler <ras...@rasterman.com> > wrote

Re: [E-devel] What are we going to release?

2017-12-09 Thread Carsten Haitzler
Carsten Haitzler <ras...@rasterman.com> wrote: > > > On Fri, 08 Dec 2017 19:06:47 -0500 Cedric Bail <ced...@ddlm.me> said: > > > > > > Original Message > > > > Subject: Re: [E-devel] What are we going to release? > > > >

Re: [E-devel] What are we going to release?

2017-12-09 Thread Andrew Williams
will be stable so we can roll a release... Andrew On Sat, 9 Dec 2017 at 12:48, Carsten Haitzler <ras...@rasterman.com> wrote: > On Fri, 08 Dec 2017 19:06:47 -0500 Cedric Bail <ced...@ddlm.me> said: > > > > Original Message ---- > > > Subject: Re: [E

Re: [E-devel] What are we going to release?

2017-12-09 Thread Carsten Haitzler
On Fri, 08 Dec 2017 18:55:06 -0500 Cedric Bail <ced...@ddlm.me> said: > > Original Message > > Subject: Re: [E-devel] What are we going to release? > > Local Time: December 6, 2017 5:22 PM > > UTC Time: December 7, 2017 1:22 AM

Re: [E-devel] What are we going to release?

2017-12-09 Thread Carsten Haitzler
On Fri, 08 Dec 2017 19:06:47 -0500 Cedric Bail <ced...@ddlm.me> said: > > Original Message > > Subject: Re: [E-devel] What are we going to release? > > Local Time: December 7, 2017 5:06 PM > > UTC Time: December 8, 2017 1:06 AM > > From:

Re: [E-devel] What are we going to release?

2017-12-08 Thread Cedric Bail
> Original Message > Subject: Re: [E-devel] What are we going to release? > Local Time: December 7, 2017 5:06 PM > UTC Time: December 8, 2017 1:06 AM > From: ras...@rasterman.com > To: Andrew Williams <a...@andywilliams.me> > Enlightenment develope

Re: [E-devel] What are we going to release?

2017-12-08 Thread Cedric Bail
> Original Message > Subject: Re: [E-devel] What are we going to release? > Local Time: December 6, 2017 5:22 PM > UTC Time: December 7, 2017 1:22 AM > From: ras...@rasterman.com > To: Enlightenment developer list <enlightenment-devel@lists.sourceforge.ne

Re: [E-devel] What are we going to release?

2017-12-07 Thread Carsten Haitzler
discussions seems required to focus us. As everyone > > > acknowledges we are a team spread very thin and if we continue to have > > > little or no direction for release we will continue to work on what is > > > interesting and not to wrap up an API that is actually usable and &

Re: [E-devel] What are we going to release?

2017-12-07 Thread Al Poole
required to focus us. As everyone > > > acknowledges we are a team spread very thin and if we continue to have > > > little or no direction for release we will continue to work on what is > > > interesting and not to wrap up an API that is actually usable and > > r

Re: [E-devel] What are we going to release?

2017-12-07 Thread Andrew Williams
ease we will continue to work on what is > > interesting and not to wrap up an API that is actually usable and > reliable > > to anyone. > > > > Right now I don't think it's clear what we are trying to achieve. It > would > > be a death knell to our chances of being taken s

Re: [E-devel] What are we going to release?

2017-12-07 Thread Carsten Haitzler
10 years to do a major upgrade. > > Regards, > Andrew > > On Thu, 7 Dec 2017 at 01:22 Carsten Haitzler <ras...@rasterman.com> wrote: > > > On Wed, 06 Dec 2017 19:45:39 -0500 Cedric Bail <ced...@ddlm.me> said: > > > > > Hi, > > >

Re: [E-devel] What are we going to release?

2017-12-07 Thread Andrew Williams
ic Bail <ced...@ddlm.me> said: > > > Hi, > > > > > ---- Original Message > > > Subject: Re: [E-devel] What are we going to release? > > > Local Time: December 6, 2017 6:13 AM > > > UTC Time: December 6, 2017 2:13 PM > > > From: dan...@oc

Re: [E-devel] What are we going to release?

2017-12-06 Thread Carsten Haitzler
On Wed, 06 Dec 2017 19:45:39 -0500 Cedric Bail <ced...@ddlm.me> said: > Hi, > > > Original Message > > Subject: Re: [E-devel] What are we going to release? > > Local Time: December 6, 2017 6:13 AM > > UTC Time: December 6, 2017 2:

Re: [E-devel] What are we going to release?

2017-12-06 Thread Carsten Haitzler
On Wed, 06 Dec 2017 15:13:05 +0100 Daniel Kolesa said: > On Wed, Dec 6, 2017, at 14:26, Andrew Williams wrote: > > Hi all, > > > > As our last release was over 4 months ago I think we really need to > > figure > > what the next release will be, and when, so we can start

Re: [E-devel] What are we going to release?

2017-12-06 Thread Cedric Bail
Hi, > Original Message > Subject: Re: [E-devel] What are we going to release? > Local Time: December 6, 2017 6:13 AM > UTC Time: December 6, 2017 2:13 PM > From: dan...@octaforge.org > To: enlightenment-devel@lists.sourceforge.net > > On Wed, Dec 6

Re: [E-devel] What are we going to release?

2017-12-06 Thread Daniel Kolesa
On Wed, Dec 6, 2017, at 14:26, Andrew Williams wrote: > Hi all, > > As our last release was over 4 months ago I think we really need to > figure > what the next release will be, and when, so we can start focusing on > making > that subsection of our work releasable. > > Clearly we are not going

[E-devel] What are we going to release?

2017-12-06 Thread Andrew Williams
Hi all, As our last release was over 4 months ago I think we really need to figure what the next release will be, and when, so we can start focusing on making that subsection of our work releasable. Clearly we are not going to get the interfaces completed any time soon. The list of things to