Minimum tasker version in XML exports

[Brett]

With the speed of Tasker's development, I fear that there will be
severe fragmentation in the install base for Tasker. A quick scan of
an exported task tells me that there is no way to know which version
of Tasker was made for, and that makes it hard for Tasker to know
whether or not a particular exported task will work with the current
version. Tasker may add a new feature in a later version, which is
used by the exported task, but previous versions of Tasker do not
support it.

Firefox uses "minVersion" and "maxVersion" to keep track of this for
extensions. Maybe Tasker could do the same?

[Emiliano]

These sounds important and usesfull

--
Emiliano

[jorgesm]

I think the only thing that needs consideration is backward
compatibility.

If you check for upgrades before importing any tasks, you'll have no
problems.