On Sat, 14 Aug 2010 17:17:51 +0200 Cedric BAIL <cedric.b...@free.fr> said:
> On Sat, Aug 14, 2010 at 3:35 PM, Carsten Haitzler <ras...@rasterman.com> > wrote: > > On Sat, 14 Aug 2010 17:27:59 +0300 Tom Hacohen <t...@stosb.com> said: > >> Hey raster, > >> > >> What's the scheduled date of the end of the freeze? > > > > ummm probably no longer than 24-48hrs or so from freeze start - less if i > > can get stuff done and cleaned up nicely. of course "shit can happen" :) > > Ok, this is really short. I am almost done with new edje file format, > but everything is not yet in and I would have liked some time to be > sure that the format is really fine. I am focusing on that right now. > > But that's not the only thing I dont consider ready for alpha. Eina > received a lot of path recently, and I didn't have time to review it > (and I don't know who wrote eina_strbuf.c but it lack a proper test > and coverage is 0). Same goes for Ecore, received too much stuff > recently. > > I would really like to see this week as a freeze week. I mean, time > for API review, time to fix a bunch of bugs and see if we are really > ok to support that API/file format for a long time. Maybe I am > misunderstanding, but when we say alpha, that means we are going to > support the API we are exposing today for a long time. > > So what do you think about having a longer period of freeze then ? well i'm almost willing to say all the eina threadsafe stuff should probably be removed for efl 1.0.0 due to its immaturity. it's not small nad this will piss stu off - but most of efl has had years of godo testing even with no test suties via things like e, elementary, freebox, etc. etc. so its rather solid. small added bits here and there are probably ok - like adding an accessor or a trivial function. some things have had api for a long time and are missing internal hooks (evas engine stuff in some cases) but the api is right (i'm pretty sure) and designed for the right reasons, just the internal support is not there yet. alpha is expected to be buggy - so fixing bugs is not something we should care about freeze-wise. this freeze was simply so we can fix up code formatting, readme's, installed files (so versions, sonames etc.) without having to wrestle with a moving target. i am not averse to having an alpha2, alpha3 etc. etc. so eina threadsafe stuff - very very very immature. not what i'd call "having stood the test of time" by any stretch. regardless if there is a test suite. api's only stand or fall by the test of time and real world usage. you get a bonus if the api designer has done it maaaaaaaaaaaaaaaaaany times before, but still is not totally there even then. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
