R.I.P..... The end is here

[nhawk]

I didn't see the vB4 notice..
https://www.vbulletin.com/forum/foru...te-end-of-life

[IggyP]

seems like mainly an official announce for the vb.com archives to me......they been saying that was the case for well around a year now im pretty sure....like i say, i take it as a green light and good news.....so long as the security patches keep coming ;P

[In Omnibus]

vBulletin 3.x is almost 14 years old. We're lucky they supported it this long. Try getting 14 years of support from Microsoft. Having said that there has been no official "end of life" declaration for vBulletin 4.x. It's users still receive security patches and support and it was upgraded earlier this year. The sky is not falling, Chicken Little.

[Mark.B]

Originally Posted by TTayfun

Don't stop the release security patch please for 3.8.x/4 series, please, We have not to update 5 series. Little bit listen your customers. @Wayne Luke.

Wayne does make any such decisions, he simply posts the announcements.

These two announcements are nothing new, this has been the case for a long time now. They simply state that no further development work will be carried out on vB3 or vB4. Old news.

--------------- Added [DATE]1514597745[/DATE] at [TIME]1514597745[/TIME] ---------------

Originally Posted by In Omnibus

vBulletin 3.x is almost 14 years old. We're lucky they supported it this long. Try getting 14 years of support from Microsoft. Having said that there has been no official "end of life" declaration for vBulletin 4.x. It's users still receive security patches and support and it was upgraded earlier this year. The sky is not falling, Chicken Little.

I'm sorry to disappoint you on that one:

vBulletin 4.X Publishing Suite End of Life

The situation for both vB3 and vB4 is the same. 3.8.11 and 4.2.5 were the final planned releases for both branches.

Support will continue as normal, with the obvious caveat that if something turns out to be a bug, or a problem caused by third party changes (such as Facebook or PayPal), then those won't be rectified as they would require development work.

All development is now focused on vBulletin 5.

[In Omnibus]

Originally Posted by Mark.B

I'm sorry to disappoint you on that one:

vBulletin 4.X Publishing Suite End of Life

The situation for both vB3 and vB4 is the same. 3.8.11 and 4.2.5 were the final planned releases for both branches.

Support will continue as normal, with the obvious caveat that if something turns out to be a bug, or a problem caused by third party changes (such as Facebook or PayPal), then those won't be rectified as they would require development work.

All development is now focused on vBulletin 5.

So, are you agreeing with the original post that the end is here? Your site still runs on vBulletin 4, does it not? Joe's site was running on vBulletin 4 last I knew. My point was it's not like sites running vBulletin 4 no longer function.

Now, if it hadn't been upgraded to function with PHP 7.1 that might have caused a much more immediate concern.

[Mark.B]

Originally Posted by In Omnibus

So, are you agreeing with the original post that the end is here? Your site still runs on vBulletin 4, does it not? Joe's site was running on vBulletin 4 last I knew. My point was it's not like sites running vBulletin 4 no longer function.

Now, if it hadn't been upgraded to function with PHP 7.1 that might have caused a much more immediate concern.

No, I'm not agreeing or disagreeing with anything, just putting the facts out there.

[IggyP]

its really better off.....dont you guys think? short of not fixing those 3rd party type new bug situations...which personally i dont think effects me much...

remember vb4 was abandoned as half done to begin with so idk where they would even start developing again....the cms? haha...seems like a clear waste of effort...but by now, it finally seems to matter less...as there are better options then those type cms stuff that never got finished anyway... i just switch off and if i ever need something like that so bad, there are wiki mods and several such options still being actively developed FOR vb4....

possibly even moreso in the near future and developers will not have to worry about having to redo their work after another vb4 release...its good news really right? ;P

happy new year lets celebrate ;P

[In Omnibus]

Originally Posted by IggyP

its really better off.....dont you guys think? short of not fixing those 3rd party type new bug situations...which personally i dont think effects me much...

remember vb4 was abandoned as half done to begin with so idk where they would even start developing again....the cms? haha...seems like a clear waste of effort...but by now, it finally seems to matter less...as there are better options then those type cms stuff that never got finished anyway... i just switch off and if i ever need something like that so bad, there are wiki mods and several such options still being actively developed FOR vb4....

possibly even moreso in the near future and developers will not have to worry about having to redo their work after another vb4 release...its good news really right? ;P

happy new year lets celebrate ;P

I think you can make any version of vBulletin amazing with the right plan and the right mindset. Some of the most popular gaming forums still operate on vBulletin 3.x versions. I think some people put too much emphasis on the most recent technology or the bells and whistles and not enough emphasis on the content. Ultimately, you can have a hugely successful blog on a single HTML page with the right content. A forum is just a tool.

[Dave]

I don't think the developers and support team members have much say on what should and should not be worked on development wise so let's not all put the blame on them.

I've personally worked on projects in the past where I got blamed on decisions that were made by people higher up.

[In Omnibus]

Originally Posted by Dave

I don't think the developers and support team members have much say on what should and should not be worked on development wise so let's not all put the blame on them.

I've personally worked on projects in the past where I got blamed on decisions that were made by people higher up.

Unfortunately, those "higher ups" are the same people who made the decisions that led the product to this point. They should condescend to speak with their customer base in the interest of the future of this product.