Merged "Will it be possible ... ?" - A collection of all kinds of questions about Kunena 2.0

Hey,
I am planning to set up an online forum with Kunena, but I am thinking about waiting with the start up until 2.0 comes out. On the website it says "early 2011", but I would like to know if there is a more definite time.

Thanks
Cymode

AS you already know, K 2.0 is currently under development. It is expected that a beta or release candidate version will be made available to the public within the next couple of months and that a stable release will follow shortly after that. The indications are that this will probably now occur before the end of Q2 2011 but, of course, no guarantees can be made at this time.

May I ask, what experience do you now have with K 1.6 and would that version suit your short-term needs in the meantime?

Hi,
if Version 2.0 doesn't come out in the next 2 months, then I will be very happy to use version 1.6. I was just worried that 2.0 might come out right after I just set up 1.6. Upgrades are always a bit iffy.

Thanks for the super fast reply.

This thread is a couple of months old and I'm wondering how much closer to the K 2.0 release date you are? Also will there be provisions for importing my PHPBB 3 data? I'm using Joomala 1.6

Thanks.

We are a couple of months closer to the release of K 2.0 than we were two months ago.

There are no special provisions on the table, at this time, for importing/migrating phpBB3, punBB, Agora, SMF, brand-X or any other froum structure.

Just like with K 1.6, you will be able to use K 2.0 in J! 1.6 to a similar extent that certain features in J! 1.6 are broken. At this time, the primary focus of the development team is concentrating on K 2.0 interoperability with J! 1.7. In other words, the aim of the project is to ensure that K 2.0 will work with J! 1.5, J! 1.6 and J! 1.7.

Joomla 1.6 is quite close to its end of life...why bother with something that will be dead in a couple of months?

As I understand it, Joomla 1.5 has been around for much too long, so people are eager to upgrade...this creates pressure on developers to make their extensions compatible with anything new out there, but really why spend working hours on something which will no longer be supported by the Joomla community in a couple of months? Who will still be using J1.6 when it is no longer supported?

As long as working with J1.6 prepares the team for J1.7 and that transition, it makes sense, but really worrying about J1.6 compatibility does not sound meaningful, to me at least...sounds more like a waste of time and resources...why further "feed" and encourage use of J1.6, apart from what makes sense to you as developers (concerning transition) ?

Which brings up the main point...J1.5 seems to be a special case with its long file cycle, but now that the development cycle is shortening, what will Kunena's policy be with regard to support of Joomla short-term releases?

Will it make sense then to spend time on probably three projects at the same time: 1) long-term (J1. 2) short term (j1.9) and 3) short term (J1.10) (and maybe even next long-term 1.11) for the time that these overlap? Or will you concentrate on long-term releases?
Since the cycle will be shorter, one would suppose the new features will not be that many, making the need or push to upgrade to short-term releases in the feature less attractive...

...So how is it going to proceed?

Cheers