Unfortunately still no ETA.
Once we have anything to share we will do so. K2 v3 is still at this moment under private dev.

Well, i must say that my concern is IF and not WHEN we will have V3.
Imagine that the first ETA published by Joomlaworks was October 2014 if i recall well.
I believe that IF the new V3 will be released, it will be close to the end of 2015.
I have no infos for that, i just state what i believe it will be the case.

We WILL publish V3 :)
That we can say for sure.

The real question is WHEN?
Many of us are developers and we use k2 for our projects!
How can I build a project with k2 if I do not have a secure update timeline?

@ K2 Team/Joomlaworks

just a thought, a short blog post at getk2.org/blog might be a good thing, firm dates dont have to be mentioned but people who havent found this forum thread might find it assuring to know that k2 is still in 'your thoughts' and active.

thanks

shoulders

@shoulders That sounds like a good idea. We will consider it.
@errevizeta You can start building it with 2.6.x and update when v3 is released.

Guys, if we go to the GitHub page for K2 v3, we see the following (as of the date and time of this post):

a month
2 months
2 months
4 months
3 months
a year
10 months
4 months
4 months

How can you honestly tell us that this is under 'active' development and its a priority given this factual information? How can a project thats apparently 'close' to being finished that only had a few things left to do, be like this?

It makes no sense.

Just come clean and admit you need help, or at least tell us whats going on.

I know I have dropped K2 from all my projects (k2 was a part of EVERY project I worked on, but if K2 can't support us and treat us with a little respect, I am not going to support K2).

It was nice while it lasted....

What i can say for certain is that either K2 V3 is not Joomlawork's priority or that the company has severe issues.
In any case i hope they will have the resources to finalize V3 development.

@John Dunstan they say it's in private dev. I agree with the rest you say.

@Florian, @Yannis It is still on private dev.
It is still in our priorities and I can reassure you we are not suffering from any issues.