Why version changes so often?

[ryukenden]

It takes time to install the new version and I wonder why the versions change quite often.

[Onimua]

What do you mean? There's roughly am upgrade maybe every month an a half or so. That's really not as "often" as it could be. Not to mention the upgrades, while recommended, aren't required.

[deathbyalfonzo]

The answer is also because often, security holes are discovered and need to be patched so people dont mess with your board.

[Onimua]

The answer is also because often, security holes are discovered and need to be patched so people dont mess with your board.

Not really the case any more with the new Patch Level system; not more upgrading.

[ryukenden]

Why not every 6 months or so? After fixing each bug, are you doing new version? It is really time consuming and to change to config file etc... is just a pain.

[Onimua]

Then people would complain there isn't enough frequent updates. Either way, no one really finds a happy medium. A month and a half, more or less, between upgrades seems to be the normal procedure, but even then there could be a longer or shorter time between upgrades so there isn't really a "set" time when an new version is released. On top of that, the software needs to be compatible with the latest browsers (Safari 3, for example), PHP/MySQL versions, etc. Every six months or more would really put the software behind everything else and people would end up complaining about not having their forum work because their host updated PHP and now their forum is having problems.

The upgrades aren't mandatory, so it's not like you must upgrade every time, or right away. It's also not like they're releasing a new version after every bug is fixed; each maintenance release has a number of template and forum bug fixes. On top of that, lately there are upgrades now to include compatibility for the new add-on products (Project Tools requires vBulletin 3.6.6+ and the Blog requires vBulletin 3.6.8+).

It's your choice to upgrade or not.

[Chase]

People are paying a lot of money for a license and they expect top quality software. That's why.

[Alteran Ancient]

You shouldn't need to change the config file at all. When first installed, config.php.new must be edited and changed to config.php. This means, when you upgrade, you over-write all existing files, replacing old for new, and config.php is not over-written, because the one that comes with the new version end in .new

[feldon23]

Not really the case any more with the new Patch Level system; not more upgrading.

I really think people need to step back and take a look at these "Patch Levels". First, it is not supported by Jelsoft to use more than one patch, so they do not make life any easier for admins than using incremental upgrades. It buys you maybe 3-4 weeks and then upgrade is mandatory. And since it does not really accomplish the goal of allowing people to apply multiple patches, it is just a confusion. How many people ask "What is this PL stuff?"

If they are going to release patches, great, but make them compatible back a few versions.

Also 3.6.7 and 3.6.8 are for compatibility with Project Tools and general bug fixes and NOT security updates.

[Wayne Luke]

Actually... 3.6.6 was for compatibility with Project Tools. 3.6.7 and 3.6.7 PL1 were security updates.

[---MAD---]

It takes time to install the new version and I wonder why the versions change quite often.

You dont need to install, you just need to upgrade by running upgrade.php (not install.php).

Why not every 6 months or so? After fixing each bug, are you doing new version? It is really time consuming and to change to config file etc... is just a pain.

I have a feeling you are installing new versions instead of upgrading to them...

Config file doesnt need to be touched unless its a major update.

[hornstar6969]

Upgrades are great! I love them! it means less bugs, and more features!