[JamesC70]

Originally Posted by Andreas

That doesn't wrok too well:

If you keep it in the category for the minimum version users will keep asking if it does also work with the latest vBulletin versions - and if you keep in in the category of the latest version people will keep asking if it does also work with older vBulletin versions.

Hence why I think it would be useful to have the possiblity to set multiple compatible versions.
(That's how it is done at vBulletin-Germany.org; we've got only one category for releases).

How about a break at 4.0 -- add-ons for 3.x series and prior are left untouched, and a new add-on management backend for 4.0 and higher? If vb.org upgrades to vB 4, then the vb.org backend would have to be rewritten anyway. So for the sake of simplicity, think of this idea as two seperate forums under vbulletin.org -- the existing one for 3.x, and a vB4 installation to support vB4 mods.

A new backend for 4.0 series mods could then take into account multiple versions, and maybe allow implemention of some of the ideas Floris and others have proposed in Hatchery.

This way the vb.org mod team doesn't have to reclassify 3.x series mods, or combine several identical 3.x series releases into one "final" release (which, btw, would break bookmarks unless the moderators left a bunch of forwarding links).