Fifteen years ago I wrote a plugin for Gramps called PedigreeChart that would create a chart specifically for printing on letter or A4 sized pages. Recently a user reached out to me because he wanted to include the chart in the Book feature for reports. That’s easy enough to do, my issue though is that he is using Gramps 5.1.
I’m still working my way through the new development process, setting up a Github fork of “addons”, “addons-source”, etc., and my question is whether it is appropriate to target my Pull Request against the “maintenance/gramps51” branch for this user. The fix works in both 5.1 and 6.0, so I can definitely create a pull request for gramps60 too.
I just want to make sure I’m following the correct process before I move forward.
@GaryGriffin has been volunteering to curate the Addons Source repositories and publishing updates to the Addon List. Tagging him here to draw his attention.
Iff the only differences in your addon code for different Gramps versions is in the Registration files, you might want to look at how the Isotammi groups manages their .gpr.py files. Example .gpr.py
They make their .gpr.py file• adaptive. There are base registration attribtes common to all version of Gramps. But it registers different expanded attribute subsets specific to the Gramps version. This lets @kku release updates across versions without additional labor.
And @ahs3 has volunteered to help shepherd developers having difficulties with navigating GitHub intricacies.
@emyoulation I will look at the example you provided. Thank you.
@Gioto Great question about the dependency on numpy. I wondered the same thing when I was looking back over my code. I will probably start by addressing the end users request first and then go back and look at cleaning up the plugin code later.