I must admit I have always had a little problem seeing the logic in having 3 versions 2.45, 2.50 and version 3 at the same time. But seeing I am not developing core directly I was assuming there was an idea behind this.

I understand we're all different people with different temperments and sometimes something is written that is misunderstod or comes out wrong in the other end, but I equally understand that it's nessesary to give air to your opinions as Critique is as important as praise.

Well I did do a roadmap and plan for 2.6 -- But I am tired of a mentally ill view that thinks for example in profile module and array could be stored in a varchar(255) -- who never present clean code, who changes are so childlike they make no sense and never offer any form of documentation or direction and just want to respond in really sickly unheathy dribble.

Mamba thank you for that explanation.

Let's be professional, courteous, and kind. This will get us a long way...

We just didn't want to leave people who are still on PHP4 with a version that had bugs, so we had 2.4.5 as a "maintenance" release. Of course, all the changes in 2.4.5 would be merged into 2.5.0.

So this is the explanation why we had 2.4.5 and 2.5.0 at the same time. A simple time overlap, while trying to be "customer driven" and taking care of our users on PHP4.

Regarding 3.0 is a different story. This will be a different architecture, while keeping compatibility as much as possible with current XOOPS modules. Since it is a major task, and kind of experimental design, DJ was working separately on this to create a proof of concept.

The idea is very simple - it's Parallel Development.

Quote:

and what about the 2.5 ajax develop by xoops france team...what is xoops next plan?...
if xoops 3.0 comes out...how it will be merge with 2.5 ajax ?

We don't develop xoops 2.5 because we do not know if our work will be included or not in xoops 3.0. We do not want to work for nothing.

This approach is also based on our experience with Skalpa and his new version of XOOPS. For those of you who aren't here long enough, Skalpa, who was the lead developer in 2005, proposed a new XOOPS version called XoopSphere. A great concept, but while he was working on it, everything else stopped, and everybody waited for this new version. After a year of waiting, Skalpa was not able to finish it due to health issues. So we've ended up without the new version, and with wasted one year because we didn't work on the standard XOOPS version.

I trust DJ that he'll deliver the new version, but we couldn't take again such a risk as with Skalpa (in case DJ get sick, or get hit by a bus, etc.). So in order to avoid this kind of risk, we've continued with 2.4.x and started work on 2.5.0.

Parallel Development works brilliant for products like cars which are changed when a new model is required. After you have started using a car you do not upgrade it to a new model. Either you continue to use the old or buy the new one. Hence the old and the new can be completely different and not-compatible with each other.

For products like CMS which needs to maintain compatibility with atleast one previous version as ppl upgrade the system (eg- from 2.0.18 to 2.3 to 2.4 and so on...) and not replace it (As in case of Cars), the developers need to work together and not independently. If they work together maintaining compatibility is easier.

In the current senerio no one is aware what will be included in xoops 3.0. So where is the motivation to work for version 2.5. Hence Kraven in his previous post rightly pointed out

I think from Skalpa case we have learnt but the wrong or incomplete lesson.
The mistake was not only that xoops stopped developing the existing system while waiting for the XoopSphere, the real problem was that Skalpa was the only one working on it. With Xoops 3.0, We have continued making the same mistake as it is only DJ who is working on it.

We really spend too much time talking about 3.0 - what it is and what it contains, while we should be working all together on releasing 2.4.5 and 2.5.0. There is so much to do here TODAY, which would help us to make XOOPS so much better, but we spend all the time on something that is still in experimental phase.

To be honest, I don't know if 3.0 will be the answer to all our prayers, but we cannot stop everything and wait for it. We've seen 2.5.0 with all its wonderful new features, so let's focus on testing and improvements, so we can release it soon.