On Sat, Aug 2, 2008 at 1:39 AM, dan sinclair <[EMAIL PROTECTED]> wrote: > > On 2-Aug-08, at 12:33 AM, Gustavo Sverzut Barbieri wrote: >> >> Guys, maybe you're forgetting about it, maybe you're hiding behind the >> "we have not released a stable version for this reason", but the fact >> is that this will happen even now. Since there was not a release, >> people just assumed that CVS is the release and that things will >> behave, because they are stable and that's how it worked so far. So >> the "pain" of breaking it now (pre-1.0) or later (pre-2.0) is almost >> the same. As I said, one can use the excuse that since there was no >> 1.0 release we're free to change everything everywhere, every time, >> but then it's just scaring developers (me included). > > 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 really think it will not be "few months down the road", really. > 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. No, I'm not. What I want is to stop cooking things that are already done. Sometimes I really think that Mark Shuttleworth is right WRT time-based releases, man, this would make this project so good, SO GOOD that I can't even imagine. From the technical to the social side. > 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). Efreet has a long list of problems: it's slow, it breaks, it depends on data structures we want to move out, etc. Ecore is big, bloated and should be split, as lots of people say so. Embryo is quite ready and useful, I can see use for it outside of Edje, mainly to extend software (ie: I'm thinking about it to map model data to row renderers on an internal project). -- 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
