On Wed, 31 Oct 2007, Hisham Mardam Bey wrote: > > So the main question I have for everyone is, what now? We're writing > code, time is passing, and we're not closing (or barely closing) any > of the items on the TODO. New features that are not always planned > make their way every now and then, and we're never substantially > closer to a release or a release candidate. What do you folks propose > we do to handle this problem? Should we freeze the addition of new > items to E17 (similar to the freeze done a while back) and concentrate > on closing all the TODO items and the bugs? Whatever decision we make, > we need to do something about the way E17 is being developed, and the > pace at which it is being developed at.
imho, a freeze would be efficient and necessary. If we decide to do a freeze, when does it strat ? When the new theme is in ? Vincent ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
