From: Mike B. <mi...@ze...> - 2011-01-14 08:35:44
|
On Fri, 14 Jan 2011 09:26:33 +0100 (CET) Vincent Torri <vt...@un...> wrote: > > > On Fri, 14 Jan 2011, Carsten Haitzler (The Rasterman) wrote: > > > OK. time for an update on this. > > > > what comes under "EFL": > > eina 1.0 > > eet 1.4 > > evas 1.0 > > ecore 1.0 > > embryo 1.0 > > edje 1.0 > > e_dbus 1.0 > > efreet 1.0 > > eeze 1.0 > > > > EFL's last go at getting ready for release was beta3. we have since fixed > > bugs and api issues and what not that we found. as such the todo list for > > efl 1.0 as best i can see is empty. tickets are either enhancements for 1.1 > > times or unable to be worked on now (malformed utf8 robustness i'd say is > > not a bug per-se more just being more robust when apps provide invalid > > input). massive multi-gigabyte images to be loaded off disk are a "so out > > there" case that i'd worry about that some other day when we have the data > > to examine. sure out documentation could be more complete and better. but > > isn't that always the case? :) > > > > so i'd say EFL is ready to go out. what i want to know is this: > > > > ... are there any issues someone wants to bring up with EFL release? > > * FIXME (there are some XXX too, iirc) in code should be checked, to see > if they are really bugs > > * static analyser (lfelipe used to run it periodically) should be > launched to see potential problems I've been running this periodically and am currently in the middle of fixing relevant reports. eina, ecore, and evas are all complete as of now, the rest will be done tomorrow. > Vincent > -- Mike Blumenkrantz Zentific: NULL pointer dereferences now 50% off! |