The Kunena team has announce the arrival of Kunena 6.3.0 [K 6.3.0] in stable which is now available for download as a native Joomla extension for J! 4.4.x/5.0.x/5.1.x. This version addresses most of the issues that were discovered in K 6.2 and issues discovered during the last development stages of K 6.3
Topics contains old discussions (generally more than one year ago or based on circumstances that subsequently changed) or topics resolved in other ways. Topics moved into this category are closed from further discussion.
Merged
"Will it be possible ... ?" - A collection of all kinds of questions about Kunena 2.0
Don't be so quick to jump on the .0 bandwagon. I like a website that works with tried and proven software, let you more adventurous types work the kinks out. Just be sure y'all document everything that blows up so I know what to do when I install .2 or .3... :woohoo:
Kunena 2.0 will officially support Joomla 1.5 and 1.7, but there shouldn't be anything that prevents it from using in J1.6.3. We are now moving our test efforts to Joomla 1.7..
So you're right: there's no point of offering guaranteed support into a product that is in end of its life. We will only guarantee that Kunena works with the latest stable versions (at the time when Kunena was released). For example Kunena 1.6.4 will not work in Joomla 1.7 because of a bug in our Joomla version detection.
So both Kunena 1.6.5 and 2.0.0 will be guaranteed to work in Joomla 1.5.23+ and 1.7.0+. They will likely work also in older Joomla releases, but we haven't tested that. They will also likely work in later versions of Joomla, but we cannot know it in advance either.
Our main interest is to support long term versions of Joomla. So we will be supporting Joomla 1.5 until it dies and we will do the same for Joomla 1.8. But after Joomla 1.8 releases, we probably have 2 versions: K2.0 for J1.5 - 1.7 and new release for J1.8, which drops Joomla 1.5 support. This is because of we would like to start using the new features everywhere and not do the same task for 2 times. Another reason is that we are using some deprecated features to save our time.
