27
I do NOT think that what m0nty is saying is arrogant nonsense. I think that yes, this situation is shifty. Yes, losing a listing on opensourcecms is a little bit of a black eye for XOOPs. And yes, full releases that can live out in the wild are preferable to patches.
But as someone who is not a developer, but just a webmaster taking advantage of a great open-source creation, I'm grateful that when problems do arise, solutions are quickly offered, even if they aren't completely plug-and-play. And black eyes go away pretty quickly.
XOOPs had a number of headaches in the last year and endured them because the community showed some solidarity. There are going to be patches and bug-fixes and security updates. I know that, however they occur, I just have to deal with them.
Now. That said, I do wish that I had realized that 2.2.3 was not intended for production sites. Maybe this was mentioned somewhere, but I didn't see it when I installed. Maybe someone can answer this:
If my version of 2.2.3 was released on 10/30/05 and is labeled "2.2.3 FINAL," is it 2.2.3a ? (Does "a" signify "final?") I can't find anything anywhere that tells me. If not, do I have to wait for 2.4 ? Should I use the "XOOPS 2.2.3 to 2.0.x" downgrade script? What's the recommended course of action?
***UPDATE*** Never mind. I installed the patch and life seems to be fine still.
Improve the time.