Hi all, As our last release was over 4 months ago I think we really need to figure what the next release will be, and when, so we can start focusing on making that subsection of our work releasable.
Clearly we are not going to get the interfaces completed any time soon. The list of things to port keeps getting longer and we have too many outstanding patches to count. I have heard suggestions that we could release a subset, for example Efl_Core and Efl_Net now that they we have the Efl namespace split into groups. This would mean releasing the API ( https://www.enlightenment.org/develop/api/start) that is prefixed efl_io, efl_net, efl_event or efl_loop and that's about it (as well as eina and eo which need to get merged into the non-legacy docs somehow). Is this a good approach? Right now it seems like we need to focus on completing portions of this and cut a release of some sort so that we can have people look at usage, bindings and porting existing code. I'd love to get our website updated to filter just the APIs we plan to release soon. And then generate another section for the work-in-progress completion of interfaces... Thanks, Andrew -- http://andywilliams.me http://ajwillia.ms ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
