There were some expansions to the plug-in framework between 5.2 and 6.0 that necessitated code changes. So having segregated collections of add-on plug-ins for 5.2 and 6.0 makes sense.
But it there a real reason why 6.0 plug-ins will not work on a 6.1 installation? (other than being a version mismatch, of course) Maybe the version compare could be “6.0 or better”?
And if a update to hundreds of addons will be necessary for the 6.1 release, is there a hack (during the beta cycle) that would let me use vanilla 6.01 addons?
This has been true for all version releases. Why introduce confusion for the average user. Running 6.0, your addons come from 6.0. Running 6.1 or eventually 6.2, your addons come from those repositories.
If a user is savvy enough to add other 3rd party addon libraries, then they should be savvy enough to get a 6.0 addon working in 6.1.
Sure. It is easy enough to tweak.
But tweaking a couple hundred (before you can do beta testing) takes time from doing testing.
But you are not tweaking the official Gramps 6.1 addons.
And you can use Notepad++ (or something similar) to batch edit all the addons you moved from 6.0 to the 6.1 folder. Search and replace within files in the folder looking for “6.0” and replacing with “6.1”.
Again, true, but it does not allow excercise of the (individual, batch or automatic) installing or updating functionalities of the Addon Manager or Plugin Manager Enhanced.
(I’m doing some hacking experiments with the GUI and Feedback of those. So that needs to interact with the rule-abiding official collection curated by @GaryGriffin… and the “wild west” 3rd party collections.)
So a “temporary for beta/alpha test” hack to allow 6.0 (or better?) would be immensely helpful.