id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
19503	Add major core version global for easier plugin/theme development	johnjamesjacoby		"'''Problem:'''

Plugin/theme authors cannot reliably use $wp_version when doing their own feature development without hitting a chicken-egg scenario.

----

'''Example:'''

I want a plugin to call function foo_32() for all major WordPress 3.2 branch versions.

I want a plugin to call function foo_33() for all major WordPress 3.3 branch versions.

3.2.1 is greater than 3.2

3.3-RC2 is less than 3.3

version_compare() is inadequate for this when used in conjunction with core's versioning scheme.

----

'''Paradox:'''

version_compare( '3.2', $wp_version ); -- Fails when 3.2.1 comes out

version_compare( '3.3', $wp_version ); -- Fails before 3.3 is released

Using version_compare() with any combination of operators yields the same result.

----

'''Proposed Solution:'''

A new global: $wp_major_version

This would get bumped in trunk when development starts on the next major version. It provides plugin and theme authors the luxury of not needing to parse the major version out of $wp_version themselves. Patch attached."	enhancement	closed	normal		General		normal	wontfix	has-patch	djpaul@… mikeschinkel@…