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. 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. 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). dan ------------------------------------------------------------------------- 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
