Abandon vBulletin 2?

[Rich]

Hello,

The people stating that 2.0 and 3.0 should be removed are those users that have upgraded to 3.5.x. Since THEY don't need those forums, they figure "why keep them".

I agree that the 2.0 forums should be condensed. The 3.0 forums should be left alone. I run 3.5.x but many people don't upgrade their sites like some of us do. Removing 3.0 at this point would be extremely premature. The amount of users running 3.0 boards is extremely high.

[Snake]

Yes, and remove vb3.0 as well.

[msimplay]

Originally Posted by iguanairs

Hello,

The people stating that 2.0 and 3.0 should be removed are those users that have upgraded to 3.5.x. Sionce THEY don't need those forums, they figure "why keep them".

I agree that the 2.0 forums should be condensed. The 3.0 forums should be left alone. I run 3.5.x but many people don't upgrade their sites like some of us do. Removing 3.0 at this point would be extremely premature. The amount of users running 3.0 boards is extremely high.

I agree as long as people still need vbulletin 2.x.x and 3.0 forums they should stay since they are still both supported in terms of updates

[darnoldy]

Originally Posted by Xenon

Hey,

i went through some thread statistics tonight, and found out, that we didn't have a new release for vb2 since more than 6 months, so i think vbulletin 2 is definitelly out of date for most user on vbulletin.org.

That's why i want to start a poll, about moving it into the archive, so we would have a clearer forumhome again (this will restrict people from posting in the vb2 sections, downloading the hacks would of course still be possible by browsing the archive)

So what do you mean?

Folks-

I would suggest--like others have--that that area be condensed to 2 areas: V2 Modifications, which should allow replies but not new threads; and V2 Questions.

Having a space for Modification Requests seems futile at this point--I would be tempted to dump them, but archiving would be fine.

I would also look at the threads in the "Beta release" section--it seems doubtful that anything still in beta would ever be further developed at this point. If a modification there is functioning, it should be included with the other releases. If its too buggy to use, it should be trashed.

Removing 3.0 is a rediculous sentiment. I own 5 licenses, 3 of which are running 3.0 due to unavailability of key hacks for 3.5.

[MRGTB]

Originally Posted by Chris-777

Removing 3.0 is a rediculous sentiment. I own 5 licenses, 3 of which are running 3.0 due to unavailability of key hacks for 3.5.

Agree'd, I use 3.0 here also, and have no plans to upgrade to 3.5 at all. So I'd hate to see support go for vB3.0. But I guess when you have vB 3.6 in the future soon. It's gonna start to get a little crowded around here with vB2.0, 3.0, 3.5 and 3.6 support boards.

I think vB2 is a little old and long in the tooth, but as already stated. But as long as vBulletin have it posted for download and are releasing support patches etc. It should be leftfor the time being.

[forumsoup.com]

I agree. Remove everything but 3.5.3 (or above).

[PixelFx]

Originally Posted by forumsoup.com

I agree. Remove everything but 3.5.3 (or above).

I'd just like to see vb3.5.3 hacks organized like 3.0.12 hacks are on the site, similar forums aka major minor addons.

I would vote keep vb3.5.3+ & 3.0.12+ sections.

[Mark.B]

Remove 3.0? What are people like me supposed to do?

I can't upgrade to vB 3.5 because too many hacks are not going to be converted, and since 3.5 offers virtually NO benefits over 3.0 to the END USER, I'd be asking my members to accept less features - no way! I'd rather wait for 4.0 at least I can justify loss of some hacks in return for new features.

[amykhar]

I contend that the 3.0 forums should be closed for posting but left open for reference.

Personally, I don't mind leaving my older stuff there for reference, but would rather not have new people install the legacy stuff which I can't support as I no longer have that version of code running.

While I can understand people maintaining legacy versions, I am befuddled as to why they would continue to modify them.