Hey guys. time to talk of our next release cycle. this meant 1.1 of most efl libs (and 1.5 for eet). this means we have lots of bug fixes and new features here. i'm currently talking about:
eina evas ecore embryo edje efreet e_dbus eeze now coming AFTER this we want elementary to go 1.0 - so this is the last change we have to "break api's" in elementary. e17 itself is an app so api is "not relevant" here, but we also want to work full steam ahead on e17 release too. what i am proposing is that everyone finish their "pending work" for everything above in the first list and get all pending changes to elm upstream asap as well. i want to call a "2 week merge window" for core efl (above) and then 2 weeks of bug fixing, then release. merge window starts next monday (24th of october). that means from the 7th to the 20th no new features can be added to trunk, only bug fixes. i am opening the floor to anyone who thinks other libraries in svn should also get the 1.0 treatment too - ethumb? epdf? emotion? some notes: eina will not have any eina-object model enabled for 1.1. evas will have all the evas-gl stuff disabled in build and install for 1.1 as its not stable yet. any more notes people have to throw in? -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Ciosco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
