I was having hopes that somewhere behind the scenes there would be some secret and active devlopment. But I must agree: when looking at the Github graph, it seems that there has been hardly any activity since December 2014 and that there are only two active developers. This is not a good sign. I have no idea what's happening at Joomlaworks, but I think I'm going to look into alternatives.
github.com/joomlaworks/k2-v3-dev-build/graphs/contributors

I love what K2 has done for Joomla, we've been using K2 for 4+ years. But the fork in the road has arrived. With no communication from JoomlaWorks, we just don't know what we're dealing with. Good luck all, hope it works out for the K2 community....

Steven Trooster wrote: I was having hopes that somewhere behind the scenes there would be some secret and active devlopment. But I must agree: when looking at the Github graph, it seems that there has been hardly any activity since December 2014 and that there are only two active developers. This is not a good sign. I have no idea what's happening at Joomlaworks, but I think I'm going to look into alternatives.
github.com/joomlaworks/k2-v3-dev-build/graphs/contributors

K2 is dead for me. And you know what, I am glad, because there is a Seblod and that is truly real CCK for Joomla! I will not use K2 even if there is gonna be a new K2 V3. Bye bye K2, for good.

Maybe we could ask someone in Brazil what happened...seems they are the only ones who really know. :-/
www.joomlaworks.net/blog/item/259-k2-v3-0-to-be-officially-unveiled-in-joomladay-brasil-2015

@Michael Yaeger: That is a good idea. But if it someone knew, wrote would previously. Uncertainty and long waiting is very undignified. We just wanted know, what happened. They are afraid?

K2 was a unique extension, at least for me. But I waited a really long time. The last remnants of trust are gone.

@Mark Schultz That brings me to an idea: I don't know what license K2 has, but maybe some group of people could fork K2 into a new component?

Steven Trooster wrote: @Mark Schultz That brings me to an idea: I don't know what license K2 has, but maybe some group of people could fork K2 into a new component?

K2 is licensed under the GPL v2, so it is open source and anyone is at liberty to contribute to it or create a fork of it. The license document is provided with the source code, so if you have a copy of K2 you only need to look at the files you already have to find that out.

The source code (including the license document) is hosted on Github here: github.com/joomlaworks/k2, from where you can easily fork it if you want to.

Its pretty obvious to me, that the company due to the problems we face in Greece in the last months, closed or having economical problems. I consider this project dead. It's something that you can easily understand it by the lack of updates. Whatever the reason of the delay would be, they could easily just post here and say that 3.0 will be released within 2016 or 2017. They didn't shared anything about it, so for me this project is dead. And Thnx god it happened before they charge someone with their upcoming premium service. Just think the possibility to have given them money and now wait for a simple reply.

Project is dead

Hello I'm from Brazil. One of the Joomla Day Brazil 2015 organizers received two members JoomlaWorks for the official launch of K2V3. very special people that have added a lot to our event.

In the lecture, they said it would take two weeks to release the new pack. After all, they had to return to Greece and finalize some details.

Something happened after that. We are unaware. (And a little worried)

We have been fairly charged for having a launch, which was not actually released. Many people ask this, but we are unanswered.

What I know is that the team was working hard on a complete overhaul of JoomlaWorks, as we talked on the blog. This would include new sites for all services, and new versions of all extensions. Also, they would open the market for Wordpress. But so far we have no feedback.

I personally am K2 user for a long time and I am also looking forward to the final version and official 3.

Given this information gap, I have chosen not to use the current version of K2 in new projects because they do not know if we will have compatibility when out an update, or if we have support within a few months.

I hope we have news soon.

Hello Paulo,

Nice talking to you again, I hope you and your wife are good.
It was a really nice experience in Brazil.

Unfortunately there were a few setbacks. I will not comment on this on this forum since people will be on my throat if I mention a date.

I am really sad to hear this from you but I assure that you will continue to have support no matter what happens.

I have personally commented many times on compatibility but since this is a huge thread my answers have been lost.

Using K2 2.6.9 or 2.7 ensures that you will be able to update to 3.0 seamlessly. I cannot however be sure about other K2 extensions but there will a 100% working upgrade method.

As for support, we answer every question on the forum (the English one), as you know my Portuguese is really really bad.

Happy Anniversary to this thread!

My guess is that some legal issue associated with this delay.
Are you JW guys diverging ideas about company future after K2v3 out?
Perhaps a problem with some (copyright) code involved in K2v3?

Nothing is slower than lawsuits ...

Hello Krikor. We're right here.

Maybe I did not use the best words. When I say support, it is not about supporting the K2 version. K2 it was always perfect.

My question is "what is the impact on templates and structure to update a K2v2 version K2v3?".

I say this because in large projects structured on K2, we make several customizations and use plugins (which work very well). Depending on the launch period of the new version, and depending on the impact that this will cause the codes, you may need to work several hours and change many things to continue functioning as before. Note that the customer will not want to pay for it from here 1 month. The risk (and cost) in this case would be mine.

For this reason, I am afraid to continue working with K2 and take this risk. I preferred to look forward to the new version.

I hope that has now become easier to understand my question.

I'm not criticizing you, just presenting a doubt for the businesses of my company.

I get you.
In terms of compatibility with 3rd party extensions, I cannot say much. It really comes down to the devs of each extension.

My advice as a professional to a professional would be for the time being, until the launch of v3, use 2.7 for production sites which require a lot of 3rd party extensions.

Do not forget that v2 will NOT be abandoned. The 2.7 series will still continue to exist and it will be supported and actively developed.
You will not have to spend countless hours updating all your sites.

This will ensure BC compatibility for users who have sites with 3rd party extensions and will allow new sites to be developed with v3.

In this thread there are several mentions of K2 v2.7. On the download page the most recent version is 2.6.9. Where can we find v2.7 and what are the differences with 2.6.9?

2.7 is the DEV version of K2 and the last major release of the 2.x series.
You can find the repo here: github.com/getk2/k2
You can download it here: getk2.org/assets/get/

The major differences (among others) include a major revamp in the UI, sh404sef integration will be moved into a plugin, introduction of batch operations (like v3), performance enhancements and many more.

Hello Krikor,

Can you explain me please, what is DEV version? DEV version is a development version, that is still unstable. It is so? About the version K2 2.7 in this thread is writes over a year...

Can I DEV version use on a live site?
When will the stable version 2.7?
The latest stable version K2 2.6.9. is for Joomla 1.5(!!), 2.5 and 3.x. In version 2.7 will be removed support for extremely old version of Joomla 1.5 and 2.5?

Best regards,
Jan

The 2.7 can be used for production sites. To be 101% sure you should backup. I personally use it in production sites as well.

The 2.x series will continue to support older versions of Joomla! while 3.x will only support the latest version.

This means that if you are stuck on an older version and cannot upgrade/ migrate to Joomla! 3.x you will still be able to use K2 v2.x.

Thank you for the quick reply. I'm not a programmer, but if will not removed support for Joomla 1.5 and 2.5, is not worse performance?