Issue queue shrinking
Crossposting from my blog.
The list of flexinode issues has shrunk a lot. I closed about 30 per day, and think I have now got a list with bugs that actually exist, or need to be confirmed.
A dynamic up-to-date list is here. By time of writing it were 25 bugs left for ‘core fields’ and flexinode itself.
Once we’ve got them sorted out (I expect half of them don’t need patches, but are simply related bugs, duplicate that are poorly described or errors on the side of the one reporting), we can release a real 4.7 version. After that, its on to a 5.0 release. From there on the real work on a simplified, well architecured version can start. Woo.
Groups:
Login to post comments
Just to say thanks for all
Just to say thanks for all the time and effort.
I deployed Flexinode on 4.7.3 quite successfully in November.
I am now in the process of testing to port my deployment to 5.x, and I cannot wait for Flexinode to rollout.
Cannot wait?
So what are you gooing to do in the mean time then?
If you help, you will speed up the release. :).