Template version control

[dwh]

The most difficult part of managing upgrades and hacks is the template doing and redoing checking and rechecking. What would be all too cool would be a version number (i.e. vb 2.2.2 for templates that originated with the latest release) for each default template. This way we could see at a glance when the default template has changed from version to version and what we need to edit and check....

If I'm not being clear enough, say in version 2.23 as a fresh start all the templates will say version 2.23. Then an upgrade comes out. So all new templates or templates that have been modified, will say version 2.24 and the earlier ones will say 2.23.

[Mas*Mind]

I like that idea :)

[Wayne Luke]

The template system has been completely re-worked for 3.0. It has more functionality is easier to use for most operations and gives you much better control over your installation.

However for the 2.X series, there will be no more new features or code enhancements. Only bug fixes are being applied.