Hi all,
To avoid getting into the same situation as the current one, I'd like
to have a plan for the next release.
I believe we should move to time-based releases such as kernel,
firefox and others do, making the life of distributions easier as
well.
Freeze: 22-February
Alpha: 1-March
Beta: 8-March
Release: 15-March (guess, if no extra beta/alpha is required)
It would be also great to define the policy of new features. With the
recent release we got some last-minute features to a codebase that was
very stable (multisense and lua for Edje), this added some turbulence
to the process and part of them were disabled at the end.
With that said, if you have big features please merge them
complete and at least somehow tested by more than you (ie: create a
branch, send patches to maillist, ...). Otherwise wait 4 weeks more
and you'll get it in! During this time you can easily keep the
aforementioned branch or patchset for broader test.
What do you think?
--
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbi...@gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
