Does this mean that in this and future versions, a developer uses "categorisation at his/her own risk. Note Umbraco 4.10 and above make use of MVC views (Contour 3.x requires it), so is your statement that you don't support 4.x overly broad?
Hope you don't mind me replying on this one since I'm not the creator of the package.
However - I think the statement should be read as 2.3.2 is the last release of the package to support v4 of Umbraco. From 2.5.0+ it's only v6+.
So you can keep using 2.3.2 on v4 but will not be able to upgrade to later releases. Even though MVC support got introduced in v4 it can be that some of the early implementations has changed / been done differently, which makes it hard to maintain support for v4 in the future.
Dropped support for Umbraco 4.x - Implications
Does this mean that in this and future versions, a developer uses "categorisation at his/her own risk. Note Umbraco 4.10 and above make use of MVC views (Contour 3.x requires it), so is your statement that you don't support 4.x overly broad?
Hi Richard
Hope you don't mind me replying on this one since I'm not the creator of the package.
However - I think the statement should be read as 2.3.2 is the last release of the package to support v4 of Umbraco. From 2.5.0+ it's only v6+.
So you can keep using 2.3.2 on v4 but will not be able to upgrade to later releases. Even though MVC support got introduced in v4 it can be that some of the early implementations has changed / been done differently, which makes it hard to maintain support for v4 in the future.
Just my 2 cents.
Hope you find them useful.
/Jan
is working on a reply...