vBulletin 3.5 Release Candidate 2
Release Candidate 2 brings vBulletin 3.5 a step closer to becoming our main supported release. Note, however, that this is still not considered a stable release, though we hope it will become so.
What is a Release Candidate?
A release candidate differs from a beta release in that there are no known bugs. However, this does not mean that there aren't any bugs. A release candidate represents a version of the software that we believe is ready for release, but requires some more testing before we're sure.
How many release candidates will there be?
We can't accurately answer this question, due to the nature of release candidate software. After RC1 is released we will wait a while to see if any new problems are discovered. If bugs are found, they will be fixed and after a period of time we will release the fixed version as RC2. The cycle then begins again - if bugs are found they will be bundled into an RC3 release. However, if no bugs are found, or the bugs found are extremely minor and require only trivial fixes, the current RC version will be renamed 3.5.0 and released. This is the 'gold' or 'stable' release.
For previous major releases like this one, we have usually required three release candidates.
Notes:
This release is almost entirely bug fixes. The only two changes of note are fairly minor:
These use the same process as all previous vBulletin 3 releases. Please refer to an earlier release announcement for full instructions.
Changed Files
As this is still not a stable release, full changed file lists will not be provided.
Bug Reports
You may report bugs by clicking here. Before reporting a bug, please attempt to recreate the bug on a default, uncustomized style (especially if your errors are JavaScript related). Additionally, if you have used the plugins/products system at all, please attempt to recreate the issue with the plugins system disabled!
Discussion
To discuss this release, please post in this thread.
Release Candidate 2 brings vBulletin 3.5 a step closer to becoming our main supported release. Note, however, that this is still not considered a stable release, though we hope it will become so.
What is a Release Candidate?
A release candidate differs from a beta release in that there are no known bugs. However, this does not mean that there aren't any bugs. A release candidate represents a version of the software that we believe is ready for release, but requires some more testing before we're sure.
How many release candidates will there be?
We can't accurately answer this question, due to the nature of release candidate software. After RC1 is released we will wait a while to see if any new problems are discovered. If bugs are found, they will be fixed and after a period of time we will release the fixed version as RC2. The cycle then begins again - if bugs are found they will be bundled into an RC3 release. However, if no bugs are found, or the bugs found are extremely minor and require only trivial fixes, the current RC version will be renamed 3.5.0 and released. This is the 'gold' or 'stable' release.
For previous major releases like this one, we have usually required three release candidates.
Notes:
This release is almost entirely bug fixes. The only two changes of note are fairly minor:
- The eAccelerator datastore method has been removed due to issues inherent to eAccelerator itself. If you are using this method, you will be seemlessly converted back to the standard database method. (More technical details are provided within class_datastore.php.)
- Product IDs can now be 25 characters long.
- Pre-release software is unsupported. You should install pre-release versions at your own risk.
- You should always back up your database fully before attempting to install pre-release software.
- If you choose to install this version, you should be aware that there may be a new version released within a very short period of time. Do not install this version if you are not willing or able to keep up-to-date with new releases.
- ImpEx does not support the 3.5 code yet, and will not support it until the release of 3.5.0 (stable).
These use the same process as all previous vBulletin 3 releases. Please refer to an earlier release announcement for full instructions.
Changed Files
As this is still not a stable release, full changed file lists will not be provided.
Bug Reports
You may report bugs by clicking here. Before reporting a bug, please attempt to recreate the bug on a default, uncustomized style (especially if your errors are JavaScript related). Additionally, if you have used the plugins/products system at all, please attempt to recreate the issue with the plugins system disabled!
Discussion
To discuss this release, please post in this thread.
Comment