What exactly does "stable" mean in programmer parlance? I haven't had whitescreen errors, and it is true that numerous "3rd" party modules do not work well with 2.2. . .

But there are lots of features in 2.2, especially those related to the member profiles module (new to 2.2) that don't work properly. PM link missing in profiles, registered users being unable to update display names and real names, etc. which have been widely reported here.

Not sure if the member profile module is considered part of the core or not. But it's features are key to the new release and they don't work for a lot of us.

Quote:

Unless I am mistaken, it is not.

During installation, you have to choose whether or not extended profiles and private messaging is installed. I believe the core team is striving to make XOOPS even more "extensible" by modularizing features that were once tightly integrated. I think this is an excellent idea. On the downside, there are bound to be some growing pains while the new API is tested out on a wide variety of platforms with a wide variety of configurations. Expecting perfection out of a major revision is a bit unreasonable. Even good ol' M$ has to go back and fix some things that may have slipped under the microscope.

In essence, "stable" means that the core developers, and beta testers did not find anything else that posed a serious functionality or security flaw. That, out-of-the-box, without "third-party" modules, it works the way it is expected to work.

In all fairness, the XOOPS roadmap for the API has been published for some time and is easily accessible by anyone. If third-party modules do not work with v2.2, it's because either the module developer has not finished converting their module to the new API, or that the module developer has stopped development of their module.

All of the above is just my humble opinion, please take it as such.

Best Regards,

JMorris