On 2-Aug-08, at 2:18 AM, Gustavo Sverzut Barbieri wrote: > On Sat, Aug 2, 2008 at 2:53 AM, dan sinclair <[EMAIL PROTECTED]> > wrote: >> On 2-Aug-08, at 1:40 AM, Nick Hughart 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. >>>> >> >> It all comes down to when you're doing the 2.0 release. If you do a >> 2.0 release in a few months it looks like we just rushed a 1.0 out >> the >> door to say we had a 1.0. Major releases should last a few _years_. >> If >> we're seriously considering ripping out Embryo in a few _months_ >> that's a pretty good sign it isn't ready to be released yet. >> >> If we know we're going to rip out Embryo and we push out Edje with >> Embryo scripting just to remove it in the next release it isn't going >> to make people happy. They'll have to port all their themes to the >> new >> scripting language. >> >> We're better to wait until we have a foundation we want to work from >> to get there. > > As I said to mekius, this will lead to never releasing, as we have > now. If we have basically 3 top components: ecore, evas and edje and 2 > of them (evas and edje) are full of potential and ideas, we'll never > release anything because they'll never be ready and all the other > packages that serve as base for them will not be released because they > might not be needed when we change something.
If we already know we're going to rip out a major subsystem it isn't time to release. Sure we can draw a line in the sand but it's better to draw the line where it makes sense. After the lua change. Not an arbitrary date for the sake of a release. 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
