> By a "future version of those libs" of course I meant a 'major' version > increase. > In any case, if you want to know why I don't think eg. evas is near ready > for a release: it's not just gradients or vgfx stuff, it's possibly smart > classes > and native surfaces that may need breaking changes, it's the soft16 engines > which > are really not ready for use (need to be replaced), it's the fact that having > evas data structures does nothing good for E (I believe they need to be moved > out > of evas and have evas depend on that lib - eina or edata or whatever), and a > few > other things. > > There is also the option of releasing things as a "pre-alpha" test > version, > and see what the reaction is, and work from there.
that's a bit what i propose when i said to release as 0.10. We keep the major release to 0 and are free to break anything for the major 1 version In addition, packagers will be happier with a 0.10 release rather than with a snapshot, which means that we can spread the efl technologies in a better way than what is currently done. Vincent ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
