Question The "longer-term" of Kunena 1.0.10

First of all I want to thank the moderator team for their efforts to collect information about problems/defects/solutions/workarounds in Kunena 1.0.10 . I do not, for one moment, want to criticise nor diminish that effort.

I am concerned, however, for the longer-term future of what has been announced to be an "end-of-life" product, namely K 1.0.10. For some people, going forward with Kunena will not be an option because they will be constrained their dependence on a specific version of Joomla and other extensions they've chosen. For some people, migrating to K 1.5 will not be possible and, therefore, they will need continued support for a period of time with the last version of Kunena that will operate in their environment.

If there's an intention to release one final J! 1.0/J! 1.5 legacy-compatible release of Kunena before the lights go out on K 1.0.x development, I should stop right here. :blush: As I have not seen any evidence of intentions to release a K 1.0.10 "bugfix" version (and to do so would derail the K 1.5 development effort) I think we should consider a better method than a "solutions/tutorials topic" in order to help existing and future new users who are contrained by J! 1.0.

Again I mean no disrespect to the moderators but I wonder if we could have some clues, please, in terms of what isses are essential bugfixes and what issues are less-critical, non-critical or merely of "curiosity value" to the K 1.0.10 user base?

I would like to help this effort but first of all I'm looking for a consolidated list of genuinely critical defects that will not be corrected in the K 1.0.x series. Can anyone help me with that, please?

It depends on the bugs found in 1.0.10. Stable Final releases have also bugs, depending on the severity of these, 1.0.x may have a service release to fix them, as well as if a j! vulnerability that could affect kunena is found.

If people are tied into J 1.0 .. which has no active development or bug fixes .. and the developer of thier critical component has gone or refusses to move on also, then surely the current K1.0.10 will no doubt suit thier needs too.

I don't see why the development team should continue to focus on a component for a Joomla version that the Joomla team themselves have essentially abandoned also. J1.6 is just around the corner.

J1.5 native support is the number 1 request on uservioce by 2:1 and sometimes "The needs of the many outweigh the needs of the few."

I would be happy to release Kunena 1.0.11, but only if someone else than me volunteers to do the hard job: collect all bug fixes to the same "build" and sends it to me.

Almost all the fixes can be found from /trunk/1.5 tree in our SVN and many of them should be relatively easy to convert to K1.0.10 as they share most of the code.

In my current situation I'm not willing to merge fixes to K1.0 tree by myself because of doing so would delay Kunena 1.5 for another week or so. I don't know how many days I have left before our new baby is born and after that I will have very limited time to work with Kunena, at least for few weeks. So I'm trying to make best use for the time I have left and trying to make Kunena 1.5.2 Stable our best release ever.

So I'm asking for your help. We clearly need to fix the worst issues in Kunena 1.0.10, but currently our development team just doesn't have the time to do it. I can lead the effort, but I don't want to spend another week or so doing it.

The best way to provide fixes to me would be to use svn:

This is how you do it by using command line:

Make your fixes, test that they work
And send the diff to me. Just remember to add comment to CHANGELOG.php what you were fixing.


For advanced users: You can also merge fixes from K1.5 tree, but that needs more skills as there are conflicts between the files. Maybe easiest way would be to checkout trunk/1.5 tree and make diffs like this:
Then you can look at the changes and rewrite them in /trunk/1.0

Diff format:
File to be changed
-[old line number],[lines to change] +[new line number],[lines after change]
- removed line
+ added line
other lines stay the same.

Matias wrote:

The best way to provide fixes to me would be to use svn:

This is how you do it by using command line:

Code:

svn checkout http://joomlacode.org/svn/kunena/trunk/1.0

it need login and password