vBulletin 4.2.2 Alpha has been released

Well things are now in motion.
http://www.vbulletin.com/forum/foru...93394-vbulletin-4-2-2-alpha-has-been-released

 

http://admin-talk.com/threads/progr...-php5-5-at-vbulletin.43880/page-2#post-496445

Merge threads?

 

It nice to see the support for the latest php version. I'll wait until its out of alpha though because they could possibly change, edit or add other things.

 

It's under software services, PHP Config on the cPanel page if that's the one he's talking about.

 

I question the "things are now in motion" statement. If they were, then you wouldn't be hearing the answers you are hearing on vB.com about the other major open issues like the CKEditor-IE10 and PHP5.5 issues. You should be hearing, "you'll see those resolved in the next versions of vB4, which will be quickly released in procession to 4.2.2", which isn't being said at all. Instead, there is again bickering between staff and customers. The cause of it all is still lack of commitment and a real plan towards supporting vB4 customers. I guess this is all a result of Bob's fantastic "agile management"?

Scott

 

@s.molinari Thanks for the link Scott. I was getting a bit down looking at the list of new comedy shows coming online this season. Then I read some of his blogs and have confidence that Comedy Central has a new comedian who is facilitating and developing some funny material. Hang on to your hats folks this promises to be a fun ride.

Everyone should have a word of the day. hmmmm Agile. Has a ring of movement.

 

I say give that update another 6 months to be released.

 

I laugh so hard, my stomach hurt.

 

I commented but I doubt it'll be approved..lol

This was my comment for the record.

 

Yeah, out of the questions Bob asks in his usual flatulent prose (which abruptly stopped to my dismay April 2012. I always liked a good laugh) , he says "learnings" three friggin times. The real question Bob needs to ask himself is, is he actually learning anything, really? Because, in my book, acknowledging mistakes first, can only really lead to real learning and faster advancement and I have yet to see IB even come close to admitting to any major mistakes, anywhere, and their actions also show no such "learning" effect either. It is the core of the demise of vBulletin.

@Brandon - exactly. What is learned by IB from this experience? How much do you want to bet vB5 will be slacking in PHP compatibility in a year or two too?

Edit - I am not one for purposely making mistakes. Quite the contrary, mistakes should be avoided, if at all possible.

However, we will make mistakes and owning up to them and learning from them means opportunity. It means opportunity to grow and opportunity to show to your customers you do really care about wanting what is right for them. Once you admit to the mistake and correct it, the next step is taking steps to avoid making the same mistake a second time. It is a normal part of a smart life and of smart business. IB and Bob seem to think showing customers they did make a mistake is showing weakness. Whereas, I truly believe, owning up to mistakes is a very big sign of strength. It shows self-confidence to be able to come back from a mistake, which might have even caused you to step backwards one or two steps. And in most cases, if you owe up to such mistakes quickly and confidently, you'll end up a few steps ahead for it in the end. This one paradigm change needs to happen at IB, before vB (or any of their products or services) can become great.

Scott

 

Did I read correctly that the reason the CKeditor is not fixed in 4.2.2 is because they don't have time to fix it... and they figure it will take at least 10 hours for their programmer to fix it?

10 hours?

What the hell have they been doing the past year?

10 hours?

Find some nerd and put him in a room with a few bottle of Jolt Cola and some chips and let him bang it out!

 

Yeah, and my point exactly. This should never have been said. The response should simply be, "the CKE changes are next in line and will be coming in an upcoming release, within the next month or two." The only problem is, I bet there is no "plan" for any next releases. The vB4 customers are being held out straws. It is total crap.

The other "issue" I can read out of that post is an enormous amount of QA time needed to test a minimal amount of coder time. That needs to change too. It is ridiculous and a waste for everyone (or QA is just a scapegoat for the slow process time). There is a reason for calling software a beta ya know. But IB also redefined that with vB5 too. Almost forgot.

Scott