Question Should I try out 1.5

Hi

I'm in the starting face of building a community site with Joomla 1.5 and Community Builder 1.2, and it will not go into production for a couple of months, or more.

My question is, should I install the Native 1.5 version and expect it to go for RC within a couple of months or should I go for LEgacy 1.0 and upgrade later.

WHat will you recommend ?

I would like to contribute with som testresults of the 1.5 if it is not totally unstable...


Regards

Allan Bredahl

Then, yes please, try 1.5 beta, the data will be valuable, but just if you can support it not being stable, taht in your case, seems pretty probable. We expect to have a RC soon. We will be concentrating devolopment fully in 1.5 branch as soon as 1.0.10 is stable

For example, i've been using the 1.5.1b for a month already on my site without major issues. But well, we are a small community and can support the bugs found (not many, mostly cosmetic)

Regarding integration with CB 1.2 will it be the same for 1.5 as 1.0. (Word is that 1.0.10 contains this integration)

Have tried to install 1.09 and made the small changes in CB to make it integrate and it seemmed to work just fine. Will try with 1.5 now.

Hi

I was about to post a similar question!

So, is this right?

Fireboard v 1.05rc2 morphed into Kunena 1.0 series, currently at 1.0.9 stable? - these all run as legacy in joomla 1.5.10

Kunena 1.5.0b is the rc for a native j1.5?

My project:
I have the database tables from a fireboard 1.0, joomla 1.0.12 site (!), and I need to migrate it to the latest fireboard, or looks like Kunena would be the go.

Is there any documentation for such a leap, or can someone help me out?

I'm guessing these are the steps, but any advice from the knowledgeable would be most welcome:
1. move the tables across
2. install latest fb-forum as per upgrade from a 1.0 site

(I have got this far before, which gives a result, but not perfect)

Then 3. upgrade to Kunena 1.0.9 with legacy on?

I have a live site to ungrade, but I can do all this on a test site on the same server first!

Meanwhile the forum on the live site is off line, so I have a deadline of asap!

Thanks in advance.....
J

Almost right. Beta and RC are 2 different things. I would not run this on any live/production site until it reaches RC an state.

As for upgrading check the documentation link for the procedure.

@farouche: I'm going out on a limb by writing this:

Unless you are an experienced/expert user, do not use any test version of software on a website where you want to impress your users! This rule-of-thumb applies equally to Kunena as to any software.

There is a lot of hype about running your Joomla! 1.5 website in "native" mode. That's all it is: hype! (see docs.kunena.com/index.php/Legacy_mode ) If you are, like me, running Joomla! 1.5 in "legacy" mode only because of Kunena, then don't obsess about it: wait until the stable, production version of Kunena 1.5 is released. In the meantime, if you implement Kunena 1.5.0b on your website - knowing that it has defects, knowing that some functionality may not operate correctly or that its performance may adversely reflect on you - know the risks that you're taking!

You may choose to implement K 1.5.0b on your site during an initial development period. However, you should realise that the final version may differ from this test version ... and you will still have to upgrade anyway. Timing will be a factor in making this decision. The experience in using a defect-susceptible version may also not be a pleasant one for you. In short, try out Kunena 1.5.0b, if you want, but don't have too much confidence in it.

Support for Kunena 1.5.0b is limited to the handful of developers who have intimate knowledge of how the programming was constructed. If you have problems, then you need to understand that answers to your requests for help will come slowly. The development team is keen to learn about errors but that doesn't imply any guarantees that the errors will be corrected in a timely manner. So, while I understand what johnnydement has written I disagree that allowing a widespread, uncontrolled public release of a beta test product is a wise strategy simply because the user base has already demononstrated that it cannot be trusted to exercise caution, understanding or restraint in handling a product that they are ill-prepared for.

I will (eventually) test Kunena 1.5.0b myself. For the time being, though, my interests lie in being assured that I am able to deploy a reliable, robust component that give me and my users confidence. For those reasons I have chosen to stay with K 1.0.9 (and K 1.0.10 when it's been bedded-down).