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

1.6 to 1.7 i dont think is a major change so most extensions that work on J1.6 will be pretty close to working on J1.7

Im no expert but i think this is the case.

Yes, that was part of what I suggested-supposed (no expert either)...but there is a difference between working with J1.6 to prepare for 1.7 (at least as long as J1.7 is not yet released), thus also preparing for the next long-term Joomla versions, and worrying specifically about the particular quirks and necessities of J1.6 compatibility...

To my mind this whole business of transition to J1.6 compatible extensions is a farse...
Who would responsibly advise anyone to install J1.6 on a professional, or at least serious website, when it took quite a few months to get this short-term release to a reasonably stable state and its end of life was vey close from the start, now only a couple of months away?

As I see it, developers should be more explicit about the lack of necessity and actual benefit of transition to J1.6 and they shouldn't encourage people to use it...not even Joomla.org uses it...that might suggest how trustworthy it is when a group of the most knowledgeable Joomla users and involved developers don't upgrade their site...or how unecessary the upgrade is...lots of tested extensions out there to make up for the bits of new features...

Because of the particular case at hand (J1.5 is around too long, people eager to use something new) most developers seem to have felt they might be left behind if they were explicit and decided that releasing official J1.6 compatible extensions (as opposed to working with it unofficially to keep up with the changes) would be a waste of time and effort (which would also cause more loss of time/resources, as people would then upgrade more readily to J1.6, if they thought they would be able to use their favorite extensions)...

But then again, 7 out of 10 people I have spoken to don't seem to know that J1.6 will NO longer be supported AT ALL a month after J1.7 is released (that means beyond August 2011 if I'm not mistaken)...
...if they knew that, if they were conscious that upgrading to J1.6 would mean also taking up NECESSARY upgrade to J1.7 and then J1.8 , with whatever problems that might mean for their website, they might reconsider...

Joomla 1.5, on the othe hand, will be supported AT LEAST 3 months after J1.8 release...

EDIT:

Let me be even more precise...

Why work making Kunena 2.0 compatible with J1.6, when the beta/release candidate version of Kunena 2.0 will likely follow the complete halt of all support for J1.6?? Who will be using J1.6 when they won't even be getting security patches after August 2011?

What I mean is, I'd much more likely prefer that Kunena 2.0 became available sooner, than having secured compatibility with a Joomla release no longer supported when Kunena 2.0 is actually out...

J! 1.5 will come to its end of life around April 2012 (assuming that Joomla's 6-month release cycle goes ahead smoothly).

I think that most serious web developers agree that J! 1.6 was a let-down and it probably will be remembered as a momentary blip on the Joomla radar screen. Let us hope that J! 1.7 is better. The early alpha release has not been very successful so far.

There is nothing basically wrong with J! 1.6. It works. K 1.6.4 works with J! 1.6.3. There are some defects in J! 1.6.3 - and that's a fact - but most people won't encounter those problems unless they really try to do some "fancy stuff". For uncomplicated websites, J! 1.6.3 is fine.

sozzled wrote: J! 1.5 will come to its end of life around April 2012 (assuming that Joomla's 6-month release cycle goes ahead smoothly).

I think that most serious web developers agree that J! 1.6 was a let-down and it probably will be remembered as a momentary blip on the Joomla radar screen. Let us hope that J! 1.7 is better. The early alpha release has not been very successful so far.

There is nothing basically wrong with J! 1.6. It works. K 1.6.4 works with J! 1.6.3. There are some defects in J! 1.6.3 - and that's a fact - but most people won't encounter those problems unless they really try to do some "fancy stuff". For uncomplicated websites, J! 1.6.3 is fine.

Sure...but even uncomplicated websites need security...they do need support...
They won't be getting any of those with J1.6 after August 2011...

So unless it's just a personal website it does not make any sense using J1.6...to my mind, J1.6 is not appropriate even then...because if your personal website is compromised because of immature security or further lack of support, there is trouble there...

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:

Regarding to J1.6 vs J1.7 discussion:

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.