On Sat, 14 Aug 2010 16:16:45 +0200 (CEST) Vincent Torri <vto...@univ-evry.fr> said:
> >> i'm back home on monday and i have plenty of things to do in eina. Mostly > >> fixes, mostly related to windows, but also new features (also for > >> windows). > >> > >> Seriously, announcing such alpha release *just* for the day after is not > >> the cleverest thing you did. > > > > i have to give a stinging reply. maybe.. JUST maybe.. you should have said > > something as a reply to my email on august the 7th about an efl 1.0.0 and > > what is blocking on it. > > did you mention the date of the alpha release ? I don't see any. I don't > blame you about a release, just that you say that there will be a release > tomorrow. One week would have been nice. > > > only replies i see from you is about my todo - which i did > > indeed update. so you had AMPLE warning. > > yes. But no date. why did it need a date? i asked what is left blocking? you stayed mum about it for a week. i didn't ask for your own task schedule and dates - simply "what is there left to do?" - no mention of what you mention now in the past week. i think giving you a week to say something is reasonable. if you have to fix internals to make then build or work on windows - i don't see that as a blocker to an alpha release. ok - then it doesn't work on windows. are you planning on ripping around with core efl api's and breaking them because of windows? are you planing on adding new features and so on that are not already there? if you are - you should have mentioned it. a new feature is not "oh - i made threadsafeness work on windows since it was now added to eina". that's not adding a feature. that's fixing a bug. it's an alpha release. it gets to have bugs. in fact it is KNOWN to already have bugs. nothing new. they will get nuked between alpha and beta. maybe there will be more than 1 alpha if the bug list takes long enough to crunch through. > > thats a week ago. not the smartest > > thing you ever did forgetting that email was ever sent. :) > > i've not forgotten it. > > Btw, the only thing i mention and that can block (imo only) is the thread > safe stuff. Which happended very recently. Other things i mentioned are > mostly related to windows. And as i said in irc, i was away during one > month. No possible commit for me since mid july. Otherwise there would > have been a lot of things i would have modified. Did you forgot that ? see above. i asked. nothing listed. being away is entirely orthogonal - and it's even better actually... it means you are unlikely to be in the middle of something :) > The way the release is done is just random. I really prefered Gustavo's > way: a plan put somewhere in the wiki. At least we were warned long > before, with precise dates. totally not random. i've sent 2 mails related to release in the past few weeks. and this is an alpha. if shit is broken - so be it. it's broken. if we made a mistake - then we made one. we have been TALKING of a release for months. if we did it gustavo's way we would have had a totally arbitray timeline that no one followed and had no bearing on reality that may have made several efl libs 1.0, 1.1, 1.2, 2.0, 2.5, 3.0 etc. by now. ask cedric about having to now maintain a whole bunch of legacy code in eet since it was released as 1.0 (which i argued against repeatedly and did only to prove a point to gustavo that it's simply not ready yet - and now we have eet 1.3.x depending on eina 0.x which isnt even a stable api or release. hooray! need i say more.). my way has meant a slow and steady move with todo lists being worked on and ticked off and things getting to the "well nothing left to do" stage which is what i was checking in on as i thought we were about there. i asked - you did not disagree or provide any information. what do you expect me to do? i did the right thing. i asked. you replied. you gave no list of things you are working on that need to be done by 1.0.0 alpha > Vincent > > >>> * no new features etc. > >>> * ONLY documentation fixes > >>> * ONLY bug fixes that are tested and work > >>> * ONLY formatting and documentation fixes > >>> * ONLY build fixes if they don't build or install things in the right > >>> place > >>> > >>> after freeze i'll be going through and removing sonames from libraries. > >>> they will also up their so version to 1.0.0. as this is an alpha it is > >>> intended to become 1.0.0 directly and the "intent" between now and 1.0.0 > >>> proper is simply fixing bugs (internally) - stuff that doesn't work, has > >>> a FIXME to finish it off, etc. - ONLY api breaks we can do from this > >>> freeze on until a 1.0.0 proper are absolute emergency ones for when > >>> something was really overlooked and we have very little choice. other > >>> than that we are on api and abi stability hiatus until full efl 1.0.0 > >>> > >>> so - you have until midnight saturday GMT (0:00 sunday morning) to finish > >>> off your4 last second stuff. if you don't get it in by then... too late. > >>> it likely already is too late now anyway. but this is your last hail-mary > >>> pass. if you are at a loss for things to do - help fix existing bugs. > >>> formatting. README's, cleanliness etc. etc. > >>> > >>> time to get this show on the road. the clock is ticking. > >>> > >>> -- > >>> ------------- 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 > >>> > >>> > >> > > > > > > -- > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > > > -- ------------- 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
