Roadmap

[we_are_borg]

http://www.vaultwiki.org/articles/72/

Thanks missed that one if its IPB ready i need to renew and see if i can help out.

[Alfa1]

Looking at the latest bug reports in the vbulletin.com JIRA tracker it does not seem like the editor will come out anytime soon.

[we_are_borg]

Well i think the editor is going to be pushed again to 4.1.5 or even 4.1.6 it can be months before we are going to see it in the live version.

[Alfa1]

That seems to be the case. And even when it is released, it remains to be seen if it functions. VW4 may be stuck in limbo for months.

I hope to see 3.0.12 in the meanwhile.

[pegasus]

If CKeditor is pushed back again, we will release Alpha 1 without it. Our main concern last month was that the Alpha wouldn't be done until closer to 4.1.4 anyway, and for the sake of a healthy testing period, we didn't want to have releases too close together. It seems 4.1.4 is taking longer than we expected, and now for the sake of healthy sales figures, we can't afford to wait around forever.

[pegasus]

Moments ago, vBulletin.com announced that it has upgraded to 4.1.4 Beta 1 and that it contained CKeditor. The site is still down to the public or I would link the announcement. This gives us about 1-2 weeks until 4.1.4 Beta 1 is public and we can get our hands on it. At that point we will add the necessary integrations and release Alpha 1 and 3.0.12.

[Alfa1]

They retracted that beta release as there were serious issues with CKeditor. They are back on vb 4.1.3

[pegasus]

They are trying again in about an hour. They are hopeful whatever issues they had yesterday have been worked out.

On my end today, working on finalizing one of the areas I personally was not looking forward to coding - replacing posts-as-comments with a dedicated comment system. Almost there, just threaded-view and the comment-editor (minus CKe) to go. What else was there ever you ask? Well basically we wrote all the save actions and other processing before we did any of the displays. This is true of pretty much every part of VaultWiki except the tools I posted in that blog entry last year.

When approaching a release, vB templates are always second to last, phrases are last. I think in general this is the way we have always worked, except this time it was a bit difficult psychologically because it seemed like we would never literally see an end result.

[dvsDave]

I'm glad you are getting closer! My users are really getting antsy waiting for XenForo, but I can't migrate to XF until vaultwiki is migrated to XF as well. Following this thread with anticipation!

[hollosch]

Hi, can you tell something about the public release date of vaultwiki 4 ?

[pegasus]

No more than has already been mentioned. We are still waiting for vB 4.1.4.

[hollosch]

No more than has already been mentioned. We are still waiting for vB 4.1.4.

Ok, thanks

[stev]

VB is now on 4.1.6, does it help VW 4's progress?

[pegasus]

Yes, as discussed here, we're back on track to releasing an Alpha very soon.

[stev]

THANKS! Could not wait for VW 4

I took the liberty of repost Pegasus' note here:

First, let me apologize to everyone, especially those who've been waiting to purchase VaultWiki or migrate their sites because they've been waiting for VaultWiki 4.

In April, we had to wait for CKeditor (for vBulletin) to be released. CKeditor wasn't released until June. It took until July to get VaultWiki working fully with CKeditor, so we could get back to VW4 development. I'm not sure how many people missed this information when it was going on, but that's where the April date went. However, at that point it was July and everyone usually takes their vacations then. So in the past 5 months, we've had a solid 1 month of development on VW4 itself. Which is, honestly, just terrible.

Customers aren't happy, and our owners aren't happy. We're now behind schedule on a lot of things at the company because of these delays. But there is an end in sight. The tracker for Alpha 1 is pushing 90%, and my personal task list for the release has been reduced to about the size of one sticky note. With the exception of 1 or 2 items, we've finished pretty much all the front-end stuff now. Just need to convert plugins and templates to the new code format, and do a round of basic testing.

We really want to get this out before the 1 year mark since development began, which is less than 20 days from now. I don't see why we shouldn't be able to achieve this, as long as nobody else takes a vacation before then. However, the tracker target hasn't been adjusted as this isn't "official" word. This is just my impression based on how we're all feeling and where we're at.