I stumbled across a post made on the clippercms site today and found it interesting to read, as an answer provided made me think.
because a lot of the feedback I see on Evo development concerns faults that should not make it through elementary pre-release testing.
People are also beginning to report problems with the continued use of PHP mysql extension, following its deprecation in PHP 5.5. I think it's a much higher priority for development to prepare for predictable future changes like this properly, rather than adding new features, however smart they may be. Making Clipper mysqli-ready involved a lot of work by Tim, myself and others...
...
I'm not sure the MODX dev crew are giving this stuff the priority it needs.
I am not sure if there is any problem with copyright here so here is the full info for the quote:
Sourced from: "
http://www.clippercms.com/forum/viewtopic.php?pid=1210#p1210"
Original author: "kp52"
After reading the post from "kp52" I looked back at some of the posts I have made over the last few months.
I have written a lot about the Evo community sponsoring the future development of Evo and have asked how things look for the future and low and behold the quote partially resembles what I have been thinking.
Take a look at the amount of times Evo has been downloaded in pretty much the same period of time the latest Revo and Evo updates were made
Evo has risen to almost a third of the Revo downloads, that says a lot to me,
a lot of people are still interested in Evo and new users must be using it as well.
But IMHO there is still a lack of transparency about what is going on with Evo.
A couple of questions:
How much development has been made to get Evo ready for the deprecation of the mysql extension ?
Is there a development roadmap ?
What do the team of developers need from the community ?
What is an incentive for the developers to get these fundamental problems sorted ASAP ?
☆ A M B ☆
☆ A M B ☆