On Mon, 18 Dec 2017 17:43:29 +0000 Stephen Houston <smhousto...@gmail.com> wrote:
> I really think a consensus needs to be reached here. The uncertainty > has too many ill effects in other areas of the project, not the least > of which is documentation as Andy has said, as well as a difficulty > prioritizing development efforts and attracting new developers. > Count me in as on the side of Cedric and Andy that stabilizing and > releasing in parts is the most ideal method. I completely disagree! EFL is a total mess! IMHO what needs to be done is EO and Wayland should be EFL 2.x. 1.x should remain legacy and X, with rock solid support. That may also extend to Enlightment with 0.22.1 has so many issues I had to stop using it. Still even some issues from EFL now show up on 0.21 when they did not before. If what exists today has issues, no one will care about what comes tomorrow. They will not be around for that. Or have any faith that what comes tomorrow will be better than what exists today, more stable, less likely to change, etc. Major changes should NOT be done in the same major version. That should be part of a new major release. Why there are major and minor version numbers. Which E and EFL seem to disregard entirely. E has never had a major version just minor. Things need to change if you seriously want to attract more developers. -- William L. Thomson Jr.
pgp6ACLoQ2sEY.pgp
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
