Kunena 5.2.4 and Blue eagle 1.6.4 released (04 Apr 2021)
The Kunena team has announce the arrival of Kunena 5.2.4 [K 5.2.4] which is now available for download as a native Joomla extension for J! 3.9.x. This version addresses most of the issues that were discovered in K 5.2 and issues discovered during the development stages of K 5.2.4
Blue Eagle 1.6.x requires Kunena 5.2.x to work with, this template isn't designed to works with Bootstrap 3 and Bootstrap 4.
Merged Kunena for J! 3.0
K 3.0 is not ready at this time. We encourage everyone to subscribe to the category Official Announcements And News About Kunena and then you will be informed, by email, when the new J! 3.0 compatible version of Kunena is available.
G'day, Mark, and welcome to Kunena.
I suggest that, to save you time in future, you try searching the forum for what you're looking for - in this case "Joomla 3" in the subject. As you can see, this is a very topical subject at the moment and your question has been asked a few times before. To those people who continue to "wonder" if (a) the current version of Kunena is compatible with J! 3.0 or (b) when will there be available a public stable version of Kunena that will be compatible with J! 3.0, the answer is in two parts:
- The compatibility requirements involving Joomla and Kunena are illustrated in the comparison table in K 2.0 Technical Requirements ; and
- General information about the proposed work schedule for the Kunena project is outlined in Kunena roadmap 2012
I note that the 2012 roadmap for K3 still gives a release date of this month. But I also know the roadmap stresses that all dates are approximate, which is perfectly reasonable
Can you give an update on the likely timetable at this stage?
Not looking to put any pressure on. We will work with whatever dates can be achieved, and would rather wait longer than have a rushed release.
This is central to the discussion. When is a good time - the time - to start to consider upgrading an existing site to J! 3.0 or, for that matter, to use J! 3.0 on a new site? In my local JUG many of our meetings have been dominated, for years, with the question "When should I upgrade from J! x.x to J! y.y?" and, even today, people often ask me "Must I upgrade from J! 1.5 to J! 2.5?"
I'm still amazed that there are J! 1.0 websites that continue to run, today, with Fireboard!
When you think about it, J! 1.6 really should have been called "J! 2.0" and we are all well aware of many problems that came with that early version, weren't we? J! 1.7 was an improvement but, even there, we were all well aware that this was not the long-sought-after long-term supported version of Joomla that we had been "promised" in 2008. In some ways it's similar for J! 3.0. There is no intention that J! 3.0 will be maintained for more than a couple of months; J! 3.0 is not a long-term supported version of Joomla. People should therefore question the usefulness of going from a known stable platform - one that will continue to be supported for the next 12-18 months - and move to something that is still in its early stages of development.
Two years ago, the Kunena leadership team proposed that the website www.kunena.org should be updated (i.e. converted over to J! 1.6) and it took two years before that work was started in earnest. As you know, it has only been less than 3 months since this website was updated and made-over for J! 2.5 and this was not an easy job. While there were wonderful new opportunities to be exploited in going to J! 2.5 there were also risks and difficulties in deciding whether it was worth our while hanging on to certain features that we were able to use in J! 1.5. We decided that it was actually better to eliminate those things that were unnecessary for our core business and concentrate on making the site work around what was vital to the project's interests. It was a difficult job and we spent many hours debating, discussing and arguing what we needed to do and how to accomplish the task. With the benefit of hindsight, I believe I can confidently proclaim our relief that we did not hasten our site redevelopment (by using J! 1.6) and that we decided to wait until J! 2.5 was available. Perhaps there are some lessons here in relation to J! 3.0, too? :lol:
Returning therefore to this most important question - when should people consider updating to J! 3.x (and therefore how important does Kunena need to be ready to work in that environment) - we could have a long (but, I'm sure it would be enjoyable) discussion about that question but this would not bring us any closer to an estimated release date for K 3.0.
The most important question in my mind (as a member of the Kunena leadership team) is the question of scope: what should be in and out of scope as far as the development of K 3.0 is concerned? I am not fully assured that we have completely resolved this question of scope among Kunena project team members. As far as I know, the only stated "objective" for K 3.0 is that it it will be the same as K 2.0 but one that work with J! 3.x and, also as far as I know, the indications are that the x has a value of "1".
From what I know about the development of K 3.0, the urgency that is driving the development effort is the anticipated release of J! 3.1 and the current indications of progress are that K 3.0 will not be released before J! 3.1 is released. These things may change but that's my current understanding of the situation.
I hope you don't mind that I gave you a discursive reply - without being able to state more surely about estimated dates for release - but such is the nature of working in an open-source software project where - like Joomla - those people who volunteer their time to produce the product have not, to date, generated a living from it. I always enjoy your questions and we appreciate the many contributions that you have made to the project. Thank you.
- Not Allowed: to create new topic.
- Not Allowed: to reply.
- Not Allowed: to edit your message.