Hello. On 24/10/16 23:01, Simon Lees wrote: > > > 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.
I can see your pain with this. One way of mitigation from the app side I have seen is that they follow up with a release on their own after a major EFL release so you have at least a matching combination. If that is enough for you to ship them is obviously up to you. 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. That sounds like it is just a matter of will to switch from one role (app developer, different team, different schedule and deadlines) to "just fixing" EO interfaces (hugely complex beast to get into already). I really can't see how holding off a release would free the resources to speed up interfaces. What it does though is cutting off our user base from updates on other areas, e.g. better wayland support. 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. I'm sorry to say but I guess that is the hard reality we have right now. We really want to get our act together and finish interfaces but it is just a huge amount of work. regards Stefan Schmidt ------------------------------------------------------------------------------ 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
