On Tue, 25 Oct 2016 07:31:33 +1030 Simon Lees <sfl...@suse.de> said: > > > On 10/25/2016 04:12 AM, Cedric BAIL wrote: > > On Mon, Oct 24, 2016 at 1:48 AM, Stefan Schmidt <ste...@osg.samsung.com> > > wrote: > >> On 12/09/16 19:01, Cedric BAIL wrote: > >>> On Mon, Sep 12, 2016 at 7:58 AM, Stefan Schmidt <ste...@osg.samsung.com> > >>> wrote: > >>>> On 10/09/16 01:29, Cedric BAIL wrote: > >>>>> I fully agree with Andrew. I have yet to review what still need to be > >>>>> done regarding Efl new interface task, but I hope that 1.19 will be > >>>>> our final call. We do now have time to cleanup example and check that > >>>>> things look fine. > >>>> > >>>> Please correct me if I did not get you two correctly here. > >>>> > >>>> You both think we should release 1.19 only once the interface work is > >>>> fully done? Be it in 3 months or in a year? > >>> > >>> I hope that we will be done by November. > >> > >> > >> You still hope this? > > > > Nope. Not anymore, should have updated this thread last week. We have > > been unable to secure someone to work on genlist/gengrid and it will > > not be done for 1.19. Blocking on efl interface to be done for 1.19 is > > now useless in my opinion (or wishfull thinking). I think we would be > > even fine with a shorter dead line. Just let me merge eo/efl/ecore and > > that would be the only really important change for this release. > > > > From a Distro / application perspective this is quite painful, what > happened with 1.18 and I guess what will continue to happen basically > every efl release a bunch of apps using eo break so they need to put out > a point release just to fix building which means that release needs to > be packaged etc.... For this reason i'm hesitant to push any eo based > apps such as enventor into anything other then an unstable part of the > distro. Atleast the showstoper based release forces those who want Y and > Z into releases to also get X done. If someone can't get this finished > basically everyone working on eo based apps are currently wasting there > time because know one can use them and they probably should be finishing > this work instead. I was starting to consider pushing eo based apps > based off the fact there would only be one more break but I guess I'm > back to holding off.
we have made it clear "dont use eo in any apps you plan to ship/release". not until its stable. i am unsure how efl can be held in any way responsible for this unless we break legacy (non eo) api... -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ The Command Line: Reinvented for Modern Developers Did the resurgence of CLI tooling catch you by surprise? Reconnect with the command line and become more productive. Learn the new .NET and ASP.NET CLI. Get your free copy! http://sdm.link/telerik _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
