Since the suggestions forums is closed.. I decided to post this here..
With the release of 2.3.1 there are numerous major flaws in the files. And just updating the current .zip would cause a support headache for you guys since so many people have already downloaded the current zip..
I'd also suggest this time for 2.3.2 that you install a public copy on the vbulletin.com server for a few days for the public to find any bugs in the release.. And then do an RC for a few extra days to weed out any bugs.. I'm sure you guys want this to be the final release of the 2.x line..
I'm not sure why this was released so horribly.. With previous releases RCs were always done first to find problems like this....
With the release of 2.3.1 there are numerous major flaws in the files. And just updating the current .zip would cause a support headache for you guys since so many people have already downloaded the current zip..
I'd also suggest this time for 2.3.2 that you install a public copy on the vbulletin.com server for a few days for the public to find any bugs in the release.. And then do an RC for a few extra days to weed out any bugs.. I'm sure you guys want this to be the final release of the 2.x line..
I'm not sure why this was released so horribly.. With previous releases RCs were always done first to find problems like this....
Comment