Hello. On 26/10/16 12:28, Simon Lees wrote: > > > On 10/26/2016 07:43 PM, Stefan Schmidt wrote: >> Hello. >> >> On 24/10/16 19:42, 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. >> >> >> Thanks for the update. I will see if Andy and Simon still have problems >> with this approach, but if not I will propose an updated 1.19 release >> plan without interface being declared stable today. >> >> regards >> Stefan Schmidt >> > > A question worth asking is what are the other features lined up for this > release and are people in a hurry to use them? Remembering that bug > fixes for wayland and anything else should be coming into the point > releases and so aren't held up if there is a bunch of good useful > features that are held up then sure release now and i'll hold off on > packaging all the stuff using eo and I guess it will be up to the > maintainers to finish off the interfaces. But if all the major new > features are centered around the newer api rather then legacy then > there's no point in a 1.19 yet as nothing can really use its new > features until interfaces are declared stable anyway.
Right now we already have 1063 new commits in master since the 1.18 release. I have no motivation to go through all of them to find out about all new features or enhancements people might want to use. Some people use the @feature tag though which can help us to find at least some things: stefan@workmachine efl (master) $ git log v1.18.0..HEAD --grep="@feature" --pretty=oneline c173be4db73326a5090d69b7442f5ebfc38f2ce4 elementary: Implement support for EFL Wayland mouse pointers a80d4ef5a54b9252c3017c858de87ac6a2a39c16 ecore-wl2: Remove usage of libwayland-cursor 0a46096337dcbde7b18e093518e3b0846a425053 elementary: Provide EFL mouse pointers for Wayland Client applications 173fda5c11fc083a0b274e404f0005a52b4bf128 ecore-wl2: Remove all references to wl_cursor usage ed2b4e97c1986e3552fc1c6fcc98eb39abb86b3f Canvas text: add annotation_positions_get method c0701a1051b94ffb018f54919dc7c462cdaac64f Canvas text cursor: add simple_geometry_get method 0566abeee85f899dffd1b58260ada696d8a86af7 Merge branch 'devs/iscaro/ecore_evas_vnc_multiseat' 63088b583c26e72223d3ff4149706b5380f0c1d4 elm_image: Add smart cbs for async open a2605240ee88a35156224be6f6dbb2f7b257fbb5 Merge branch 'devs/devilhorns/atomic' b242f50626c57212d2b6525d8bddc8f0595971f4 Eo: introducing libeo_dbg.so. 1d26e614789a598c7562a4e826a80b74f6f45d60 eina - add recursive mutex lock - apparently these are portable a2e3b8ad134b7170dbd0ae585b331d87aa694cb6 eeze: add support of GPIO sysfs detection and watch. 9c779dca90bea36ad43c77597f107dd157a33c46 Rename efl_self to efl_added 4aae224ef5af35e920e0c5a2c23df9afbb33bb84 Efl object: change the way we set class's functions. b3993b684e30bf20fca66cf25308f627420a199d win: Add EO API to query state of multi touch points d88f08f7e92a06ce114466da41886463be58c8d8 eina: module - Add macros for adding module informations 60526528a6cc85050a74d5d45f6502ea5c07d70f evas: Add normalized and window coordinates to axis events 834794ed84d737e394c47fc4145a0219f7124b01 evas events: Add new "finger,move/down/up" events for multi touch a016ab751c4875d66e7c7c8dd5c5272a6f03f084 Static deps unibreak: Update to latest git version. 2462f1d47b32a57613bbc42ebb117a5247377452 Efl object: Remove creation of event structure and passing it to eo. 922a1bcd9e667e6d3d47df12f49d91a7351f3fe0 evas: Add support for region load with PNG files a76fd7b37e464c45528b9077cbd2e261bda60f9b evas: Support region_set for BMP image 28c80f91221ae2639f4573046d8621a2a4d18cda Efl object: implement CoW for the function vtables ae3ac0cd2520469c700d43c81e33534ce0d8e92e edje: Allow no_render in description cb24d5f4896e1b17b5d61f437635c6024d953b2f eina: Set EINA_ERROR_TIMEOUT to cond_timedwait 471a328ea0e5607f25391496b76aafedeb34a79f edje_embryo: add function to know swallow has object Ignoring all the commits which might have good new stuff but are not tagged properly we already have vnc multiseat support here, EFL mouse pointers for wayland clients, region load and set of image files, smart callbacks for async open of image files, etc. > After the interfaces are stable I think it does make sense to go back to > time based releases. If everybody else wants to release now thats fine > i'll just put off packaging any eo based app until I know which release > the eo interfaces will be stable in. > To be honest I'm getting a bit tired of the discussion. If we do want to wait and pray so be it. If we want to release now, November is the only month I would see a chance to get the stabilization done before we could make a release. December is hard to get anything done with end of year closing, reporting, vacation, bank holidays, etc. In January I'm unavailable for half of the month. Which makes February the next possible stabilization month with a potential release in March (making 1.19 a 7 months release). I'm not pushing further for a 1.19 release this year. If people do not care, did not make up their mind or agree that waiting is the better thing to do, we will wait and I bring up the same discussion again in February 2017. 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
