Hello.
On 08/07/16 03:37, David Seikel wrote: > On Thu, 7 Jul 2016 13:18:55 +0200 Stefan Schmidt > <ste...@osg.samsung.com> wrote: > >> Hello. >> >> >> On 07/07/16 12:53, Simon Lees wrote: >>> On 07/07/2016 06:08 PM, Stefan Schmidt wrote: >>>> Hello. >>>> >>>> >>>> Nobody can be fooled here, we are late. :-) >>>> >>>> >>>> While the big merges of Elementary, Evas Generic Loaders and >>>> emotion Generic Players went better that I expected we are running >>>> out of time for interfaces. >>>> >>>> We delayed and hoped we would get in done and could still put it >>>> into 1.18, but looking at it now that seems impossible, if we do >>>> not want to delay even longer. >>>> >>>> >>>> So here is the new plan. >>>> >>>> o If you have some loose ends with a _realistic_ chance to get >>>> fixed you have the next week for this. >>>> >>>> o We switch EO and all interfaces back into BETA, all new code >>>> stays as is but is not officially released. >>>> >>>> o I will do the hard freeze and alpha release on Monday 18.07 >>>> (tentative date). >>>> >>>> o After that we try our normal 4 weeks stabilization window (my >>>> glass ball is a bit dusty so I have a hard time to predict if 4 >>>> weeks are enough here) >>>> >>>> >>>> Any objections or comments? >>>> >>> The downside to this from my perspective is there are certain e21 >>> features that are using this api conditionally compiled out (I >>> think the new gadget system), currently i'll be taking 1.18 into >>> the next openSUSE release which means these features won't make it >>> to e21 in that release so from that perspective for me if the >>> release takes another month to get out right that would be better >>> but if its going to take much more then that then it would be touch >>> and go as to including it in the release anyway so if it will take >>> longer then that additional month it may as well be done now. >> OK, this is getting a bit confused. For everything wayland or drm >> this should change nothing. These parts do not use eo and will stay >> as they are right now for the release. >> If parts are marked as beta aright now they would so for the release. >> If they are public APIs they would also stay this way. >> >> For e21 doin a release now would actually help. >>> The other thing to note is this week there seems to have been a lot >>> of testing going on and fixes going in that along with the fact >>> that most apps in existence arn't using the new api's anyway maybe >>> with another tech preview in the next 2 weeks before the api's are >>> finalised we could cut the stabilization window back to 3 weeks. >> With promises not being settled we still have a long way to go before >> the new APIs are in a stage where people would start using them in >> their application widely. > For what it's worth, my big experimental 3D world project tries to make > use of a lot of this new EO API stuff. It's a wide application that is > not widely used, yet. B-) > In which case this should not really be a big problem for you if we move these APIs to 1.19 to become public, right? regards Stefan Schmidt ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
