The better question is, will it be released with any kind of quality? But to answer your question, I'd say it should be out next year, probably second quarter. Scott
If their recalled new framework is as good as they claim , then theoretically it shouldn't be hard to do so. Only specific task they will need to inherit main nodes for functionality and create new templates for design. P.S : I still didn't check their new code and have no intension to do so
Would love to see your opinion about the code my experience in PHP and so is to low to see most mistakes.
Because as we all know, vBulletin 5's 'gold' version is anything OTHER than an unstable Alpha Release of the software! Guess the differences are only in the description...
Does anyone know the exact number of "fixs" there has been for VB5? If I remember correctly, a figure of over two thousand was mentioned and there seems to have been many more since then. So possibly over three thousand, and it is still not officially classed as "Gold" and probably never will be. Is such a number normal for new versions of this type of product?
What does it say about the software and development process, when so many issues have been fixed and the software still isn't accepted as a good quality product? Scott
More like: Hahaha jk. When isn't connect unstable. I feel like it always says it's not recommended for production use. Will it ever be?
No doubt it will be more expensive as it will also be the "platform that all others will be built on" Naturally if you just want an earlier version you will be forced to pay the inflated price for V6.
Oh God, vBulletin 6 as a concept kind of scares me. I mean, if they messed up vBulletin 5 this bad, I wonder what vBulletin 6 will be like?
I could be wrong but a little birdy told me, or was it a flying pig, that because vB5 is such a debacle they have opted to relegate it to the delete folder and start a fresh with vB6. And, and, dejected SMF devs are going to assist cause all the good vB devs left or were let go.
Hahaha so true. And then there will be another vulnerability that compromises 99% of vBulletin forums on the net. They just can't seem to get that part right yet..
I don't know if anyone has heard of the vBulletin upgrade vulnerability but it was 100% their fault. They added a customer ID login to the upgrade.php script. But they also embedded the customer ID hash into the page source and pretty much linked to the hashes algorithm.
If the VB support staff stay true to form they will say it is the customers fault for not all being techs and being silly enough to buy VB without spending a lot of time and effort checking it to see if it is a good program. The antics of IB and VB are now becoming high farce. Any credibility they may have had is gone. VB staff hard at work on V5 and V6.