Closed tivnet closed 8 years ago
In the hook loading, still need to worry about the major version changes.
So, probably, we need both: class name matching the major release # and the hook loading.
@slaFFik If you confirm the WP_Requirements_2
change, we should do it now before the develop
is merged with master
.
How about keeping both the old wp-requirements.php
and the new wp-requirements-2.php
in the repository? Those who need and want to upgrade will modify their code. This should solve the backward incompatibility problems, because, with each major release, we'll make a new file and new class name.
► Still need the hook
loading to get the latest minor release.
I agree with the arguments and a proposed solution here :)
@slaFFik Please check the implementation and if OK, let's make it 2.0.0
Note that the old class is kept as-is.
Two options:
WP_Requirements_2
now. This means that any additional functionality will bump the major release. Not practical, probably.hook
loading of the class (similar toCMB2
).