On Sat, Aug 2, 2008 at 2:40 AM, Nick Hughart <[EMAIL PROTECTED]> wrote: > Vincent Torri wrote: >> On Sat, 2 Aug 2008, dan sinclair wrote: >> >> >>> I'd say you're so eager to release something you're not thinking about >>> the impression it gives. Changing things in a pre-1.0 is fine and >>> expected. Releasing a 1.0 and then breaking it or making major changes >>> a few months down the road is a very bad impression. >>> >> >> I don't think that if we release a 1.0 soon, the next the next major >> release wiil be out in a few month. It will follow the same release >> process (some years) >> > > The problem is, the two issues that have come up that are being > considered as blockers are things that may affect how many people want > to use the EFL. So waiting 3-4 years after a disappointing release may > just push people away. We should at least try to address the > shortcomings now or people will either have to wait years for the new > release or get a release so soon that they have to readjust everything. > Either way, I'm sure they won't be happy.
That's just PLAIN WRONG. This leads to infinite, because there is no such perfect code ore release, leading to what we have now: never release. We must put a deadline and honor it. It's very similar to what Gnome and Kernel guys are doing, and its working. It's what Mark is trying to push and I really like it. Things like Edje and Evas have great potential and will never calm down, people will always come with ideas, suggestions, rewrites and all we know, much like Linux Kernel. If we don't specify a time-based release we'll never release, because the todo/features list is always growing. >>> You're releasing something before it should be released just to give >>> the impression of a 1.0 for something that isn't 1.0. That leaves a >>> worse taste as a developer then holding off the release until we're >>> pretty sure what we've got will be it for the long haul. >>> >> >> Explain why you think that current efl can't be considered as 1.0, please >> >> It seems that you have the same opinion than raster has about >> enlightenment, that is enlightenment will be 1.0 when there will be no >> more improvements he will be able to think about. >> >> What the problem with doing releases ? It helps packagers and users, >> people that use commercially the efl are satisfied because they know they >> have a solid base set of libs they can work with. >> >> >>> If you want to push something out the door, what about Efreet, or >>> getting Eina done then doing Ecore. We don't have to start with an >>> Embryo release. We don't have to push Embryo until we're ready to push >>> Edje. Pushing Edje has to wait until we push Evas (which also has to >>> wait for Eina). >>> >> >> Heh, I would like to release all the efl as 1.0 (maybe after the eina >> move). Then, in a few years push the 2.0 release (for e18 ?). There are >> *lots* of stuff to do for a 2.0 release for evas and edje (i don't really >> know for ecore). About evas, you see the discussion between mainly Jose, >> Jorge and raster. About edje Gustavo told me that raster has huge plans >> about it. So why not writing edje 2 with these plans and with another >> scripting language than embryo when thee plans will be known a little bit >> more ? >> > I've made a similiar argument for EDJE, push it as is with embryo and > don't expect the flash/silverlight/etc crowd to jump on board right away > and make user interfaces. Use EDJE for what it can do now and then in > the future we can do a 2.0 release that adds the extra stuff. But by > that time, people may have throughly invested in embryo and it may cost > them quite a bit to change all that. As I said, it already happened, don't hide under the "we did not official 1.0 yet". -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: [EMAIL PROTECTED] Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------- 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
