Hi Paul,
Automated testing/CI are a bit beyond us at the moment.
But, I think the gist of your suggestion lines up with Michael's: the codebase does not necessarily need to reflect the Moodle version compatibility, as long as we are documenting that information somewhere else in our workflow.
In our case, this is especially true, because we are not releasing anything on the Moodle.org repository at this point. If we were releasing it publicly, conforming to a couple more conventions would be helpful to others using the plugin, but for purely internal use, we can afford to be sparse. Thank you for your thoughts!
- Ray
Automated testing/CI are a bit beyond us at the moment.
In our case, this is especially true, because we are not releasing anything on the Moodle.org repository at this point. If we were releasing it publicly, conforming to a couple more conventions would be helpful to others using the plugin, but for purely internal use, we can afford to be sparse. Thank you for your thoughts!
- Ray