Hello, As the time comes, we are trying to move to a time based release. But as the discussion on Eo does show, it takes time to reach a consensus on some API and make it difficult to move forward on a release.
So I have introduced a macro EFL_BETA_API_SUPPORT that is used to disable API that we won't support for the next release, but still want to push forward. The people that want to use those API should be advised that they will have no ABI/API stability on such API and will need to enable it manually. I have added a m4 macro that will add it to the config.h at configure time. The first API that I have just marked as beta is Eo. All program that use are now using efl_beta.m4 (elementary, expedite, clouseau). The goal is offcourse to have the least amount of those API in beta, but that is I think the only sane way to move forward. Regards, -- Cedric BAIL ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
