Re: [e-users] Where are we?

[Carsten H. (T. R. <ra...@ra...>]

On Fri, 10 Mar 2006 11:47:35 -0500 Mitch Gorman <mg...@cb...> babbled:

>     Hey, Carsten, not to put you on too much of a spot, but I'm just 
> wondering:  where would you say e17 is, right now, w.r.t. an official 
> (v1.0?) release?  I think I've seen you say things like "we're not 
> adding any new features anymore"... that would seem to indicate that you 
> feel like you guys are closing in on releasability.

no new features for 0.17 release. only what's in the TODO - if it's not in TODO - it's not happening UNLESS it's an obvious oversight and it's not too hard to manage.

>     Like (I'd guess) most of us, I'm a developer, and I'm certainly not 
> going to let the tag "pre-release" scare me off of using a piece of 

the tag is meant to scare off "users" - not developers. we don't need to be giving personal tutorials on how to change your own WM 327 times a day when we are doing development :) even on release that should then be formalised so its done FOR the user automatically by some install wizard.

> software (the first Linux kernel I built was 0.97pl3, IIRC), so this is 

ok - you're ahead of me. i started with kernels at 1.3... :) though i was hacking up x apps before that... as i had no linux machine yet :)

> just idle curiousity.  If you say e17 is "90% complete", that's great; 
> of course, if you say "40% complete", that's even better, b/c it means 
> we can expect/hope for a whole bunch more GUI goodness still to come 
> before e17 is "done".

I am not  putting a % on it (i actually hate the numbers - they are mostly "pull it out of your arse" numbers anyway) - BUT there is a TODO file in the source with things to do... and things get taken off that list slowly as they are done. i imagine i will add a whole bunch of niggly fiddly things at some point in a "needs polishing" section (ui's badly laid out, little quirks we need to fix etc.). and basically as that list of things goes to being empty - that is your indicator of getting close to release. right now my policy is that we can pump out official alpha releases when all TODO items are done EXCEPT for bugs. bugs will be fixed along the way and during alpha - and new bug reports will come in.

During this cycle e might release 1 or more alphas with each having a reduced set of bugs (hopefully) until we have cleared all known bugs (ie last alpha is released and lets say after a week we heard of no bug reports). then comes beta - same cycle. beta though will last longer (a few weeks at least), gather bug reports, and fix up real polish stuff like install documentation. all packages (.deb, .rpm etc.) should be ensured to be of top quality, correct etc. etc. we should prepare pre-compiled binary installs (i have one such test binary already hat is a self-extracting .run script), make sure the website is all geared up for a pending release, etc. etc. - then release an RC1, and more RC's as needed then a final 0.17.0 - then it's time to sit back and watch the flames :)

>     Care to hazard an estimate?
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> enlightenment-users mailing list
> enl...@li...
> https://lists.sourceforge.net/lists/listinfo/enlightenment-users
> 


-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ra...@ra...
裸好多
Tokyo, Japan (東京 日本)