Some addons are backwards compatible, needing only version specific Gramps Plugin Registration file (.gpr.py) customization.
Could a new plugin registration feature be created that helps with releasing backports?
- Some addons developers are maintaining separate .gpr.py files and .tgz archives for each compatible version.
- Some are using a .gpr.py file with code that adapts to the attributes needed for major version. This allows all versions to use the same .tgz archive file
The second method entails some untested compatibility risk. Does backporting compatibility go all the way back to 4.2? It is more likely that it only goes back to 5.2
What can be done to make the backporting more automated for the make.py that @GaryGriffin is using to generate the Addon Manager compatible .tgz and .json files?
Example: the DescendantSpaceTree report was just published for 6.0 but is backport compatible with just changing the gramps_target_version attribute in the .gpr.py file.