vBulletin Tracker update

Everyone,

As part of an overall audit of unresolved issues that have been reported on vBulletin in our tracker, we are beginning a process of reviewing all open (Confirmed) bugs reported on versions prior to 4.1.
This process will involve moving outstanding bugs to an “Unconfirmed” status starting with the oldest reported bugs – our bug scrubbing team will then work through these bugs and “confirm” bugs that are still found in our product.

Cool, why?
The intention behind this project is to remove duplicates of bugs that have been reported, as well as remove bugs that have been reported in older versions but have since been fixed – but their status does not reflect this.

How can I help?
If you see a bug that has been moved to “Unconfirmed” but the bug is still present in latest released version (4.1.3), please comment in the bug report that it is still in the product

Thanks,
Adrian


Continue reading...

 

Oh, you mean that they are actually going to start patching stuff and fixing things in their tracker rather than causing more problems, oh the shock of it...

 

Haha, that gave me a good laugh <--- The solution to the vBulletin problem.

 

haha...