Conversation
|
I am +1 to remove that, the more features we add to plugins registry, like the universal plugins, makes this a bit harder to maintain. Also, nothing prevent users to either install .gem or to define |
ph
left a comment
There was a problem hiding this comment.
Changes LGTM, waiting for travis to run the job.
|
OOPS I havent read the WIP state on this PR, what do you think its missing @jordansissel ? |
|
what I think is mainly missing is the docs I want to provide to users to upgrade -- specifically, a path for users to go from the old style to the new style plugins. |
8d851c6 to
404197c
Compare
|
Added an issue for the upgrade docs #7677. I will merge this one to 6.0 and 5.x. |
|
This pull request does not have a backport label. Could you fix it @jordansissel? 🙏
|
|
|
|
This pull request is now in conflicts. Could you fix it @jordansissel? 🙏 |
I've intended to deprecate old-style plugin (older flag --pluginpath, --path.plugin) for years. Let's do it now :)
Details and discussion are in #6200
My intent primarily is to deprecate this feature, not remove it entirely, by doing the following:
Todo: