Quote:

I have to insist and ask again, when will xoops 3.0 alpha be released?
Last time I asked you about it (in one of our few messenger talks) you told me it would take 2-3 months. I added one more month into your calculation and I took for granted that 3.0 would be released in march.
I was disappointed and still am. When the matter is trusting people, I never ear third party opinions, people will have to fail on me to loose my trust.
I will ask you one last time to give me(and the community) a release date, please.

@ Bjuti
Quote:
As stated here by DJ, the current modules should be compatible with X3

please merge 2.45 + 2.5 + 2.6 + 3.0

asap


an announcement actual date of an alpha 3.0 release will be nice

2.4.5 is a must, coz 2.4.4 contains some bugs! Then 2.5 ASAP, and no 2.6, just 3.0 alpha in a month, beta in september, final in november. Xoops have no time.

Quote:
Where did you get these versions? And why should they be merged? There is nothing to be merged.

As I've mentioned here, we are working on three versions right now:

2.4.5
2.5.0
3.0

The 2.4.5 is a maintenance release, and it's the end of 2.4.x series. The RC2 It should be released today or tomorrow, and a final release hopefully within a week. Then there will be only two versions.

The 2.5.0 is the main one that we're working on. Any bug fixes from 2.4.5, will be added to 2.5.0, if needed.

There is no 2.6.0 version. Wishcraft posted some ideas about future features, but no work has been started, and there are no plans at the moment for starting any work on this.

The 3.0 has a new architecture. Since it has a different architecture, the previous releases cannot be merged into it. The only thing that we'll be focusing on is to ensure that current module work on 3.0.

I hope, it clarifies it a little bit more.

What about Smarty 3.0 (now in RC stage)? In what version it's gonna be implemented?

Tnx.

Quote:
I am sure that the 2.5.0 Team would test it, and if the tests are positive, then it could be included in 2.5.0.

But it would be up to the team...

@ nmshah
Quote:
I would hope that you would give me some credit that after almost 6 years on the project, I understand at least some of the problems here But sometimes throwing the baby with the bath is not the best solution!

So please be patient and I'm sure that we'll get there all together.

I understand the frustration of some developers, and as DJ said, I've been been harassing him for the last 6 months for dates. And I want to believe that we're getting close to the end of this journey, when 3.0 Alpha will be released.

But as much as we want it "right now", we cannot forget that we are all volunteers and we're doing the development in our free/spare time.

It saddens me that we so often just "demand" things from those poor souls, regardless of what is happening in their personal lives. Do we know if somebody died in their family? If they lost their job? If a new baby was born? If they got married and got divorced? Or if they got sick?

Let's show some compassion for each other, be kind and respectful. Instead of demanding "Why didn't you do it yet" maybe asking "How can I help you" would be a better approach in this Open Source environment.

Quote:
Well, why are you still "just a user"? Why can't you become a documentation writer? Or a tester? A member of the support team? Why not join a team and make XOOPS a better CMS?

Come on guys - XOOPS 2.4.4 has been downloaded over 30,000 times in the 4 months since its release (incl. international versions), last week we have crossed the mark of 100,000 registered users on our Website.

The new Themes Demo site rocks thanks to Burning, Burning is working now on updating the repository, every week we're getting new modules and themes, probably the most ever within the last 2-3 years.

So many good things happening, so let's be a little bit more patient.

Quote:

if i understand this correctly...

so what is the point of continuing 2.5 version if it can't be merged with 3.0 ?

so two main version 2.5 and 3.0 ?

i would like to see the more improved jquery block management of the 2.5 version in 3.0 if thats possible

Because 2.5 could be released next month or two, and with 3.0 we don't know yet when it could be deployed on production site, since we don't have even yet alpha.