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.

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

You are or you are not ?

HAhahah no :)

We are not. I am also editing my post.
Thanks for pointing this out.

Could you give more information please.

In this topic you have said that it is in private dev and you say there are no issues but we are 6 months over the dates you gave when you stated it was close to completion with a few more tweaks.

These statements don't seem to make any sense.

Are you starting from scratch, have you hit coding issues, are you tied up with other client work or is there some other reason.

I can understand people getting frustrated when there seems to be no information and then the only information is 'everything is ok, it is in private dev' when this does not seem to sit with previous communications. Someone somewhere must have decided to put the release back for some reason, the community just want to understand what is happening and why then we might understand what is happening.

I'm not trying to be negative and I would love to be able to subscribe to a commercial subscription if it would help get the project finished (and I'm sure others would) but if you leave it much longer I'm not sure how many of the current/old user base will be left.

Looking forward to any explanation.

Cheers,

Dave

K2 3.0 is written completely in different code structure. So whosoever is using K2 2.6.9 with custom template would have to re-design the whole template when K2 3.0 final release. New project developers are feeling confusion in their mind whether they wait for K2 3.0 or build the project with 2.6.9.

The templates that you are using will be compatible with 3.0 if they are up to date.

I cannot however tell you anything about template frameworks or 3rd party extensions.

Now @inblackflag the complete code restructuring is mostly for the backend. Users with existing K2 sites will be able to upload. Since K2 is used by thousands of users Backwards Compatibility is a priority.

@Dave Sage Thank you for feedback. A longer statement is indeed needed. You are right. I personally cannot share any info but expect a detailed explenation/ blog post soon about this.

Actually I was thinking, what is the advantage to add k2 to Joomla 3.4.1?

The new Joomla version contains most of thing that k2 offered in the past, perhaps this is the most important thing that we should disscus

Thanking you in advance.

Extrafields, which is a huge asset.
Templating.
Commenting system out of the box.
Galleries and videos in your template and not inside your editor.
Proper tagging (no point in tagging your users or categories.)
User's page
A dozen of option so you can create multiple subtemplates and views.
Optimal Performance

These are just to name a few :)

For all this we don't want the project to be dropped :)

Your lack of communication and your inability to keep promises leaves me/us speechless!
You are not even able to keep a simple promise such as writing a post on your blog to explain the reasons for this delay!

How is this story going to end?

All Quiet on the "K2" Front ...