Missing auto backport feature

[tttp]

Hi,

Follow up on the sprint discussion an extension compatible with several versions.

Imagine there is a new generic tpl/code that is added into 4.4. You can use it in your extension directly on 4.4, but won't work on 4.3 (and you need to support it)

So the alternative is either to code for 4.3 and miss the feature (sucks) or add in the extension CRM/templates the 4.4 files to backport it (sucks slightly less). The later being an issue as it won't be automatically replaced if a better version is upgraded in the core.

What about adding a backport feature?

new folders backport/neededversion/CRM|templates|api/....

on install, civix compare civicrm version with backport/neededversion, if >= does nothing, otherwise, copy the files to CRM or templates

X+

[totten]

I think this less important in a LExIM world -- since there's one mainline branch, and new APIs can added to it fairly quickly.