On 10/26/2016 07:57 PM, Stefan Schmidt wrote: > 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. >
The problem is perhaps harder the other way as in a openSUSE stable release we won't update to a new feature efl release we will only take the point releases (One of the reasons I created LTS for efl and e). This means that if any of the eo based apps do a bug fix release after 1.19 is released they will probably also include the eo interface changes as expected which means that I wouldn't be able to use that release. For this reason none of the eo based apps will be in the upcoming release but I was preparing some of them for the release after as this was going to be sorted by then but now i'm less sure. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adeliade Australia, UTC+9:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ 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
