Originally discussed in #618, this issue acts purely as an overview of all the issues related to creating standalone plugins for the modules that are currently part of the Performance Lab plugin, and then removing the corresponding modules from the PL plugin in favor of the new standalone plugins.
Milestones
This effort should be broken down into 2 milestones:
- Publish the modules available as standalone plugins
- Remove the modules from the plugin
The first milestone will unblock the more urgent goal of having standalone plugins for every performance feature project, as well as therefore having a clear path forward also for new features.
The second milestone will ensure those standalone plugins are the canonical way to test those features, with the Performance Lab plugin still providing supporting features e.g. related to performance measurement and management of the performance related features and their plugins.
While the first milestone does not change anything notable for existing Performance Lab plugin users, the second one will require administrators to install/activate the new plugins and can therefore be considered a breaking change. As such, the second milestone should eventually be released with a major version number change, as 3.0.0.
List of issues
The list below includes all related issues, somewhat ordered by their intended sequence of execution. Important to note:
- Some of the issues can be worked on in parallel.
- The issue for milestone 2 can be defined as milestone 1 is being worked on, however milestone 2 issues should only be implemented / merged after milestone 1 has been completed.
- The list is not necessarily comprehensive, more issues will be added as needed.
- You can always get a list of issues also using the "Creating standalone plugins" label.
Milestone 1
Milestone 2
2a (2.8.0 release)
Follow-up PRs:
2b (3.0.0 release)
2c (3.0.0 release polishing)
Follow-up Issues & PRs:
See #911 for somewhat related discussion, which however is not a blocker to this effort. Additionally, documentation for how to write a module will need to be updated after the 2b changes, and basic documentation for how to start a new plugin in the repo should be added too.
Originally discussed in #618, this issue acts purely as an overview of all the issues related to creating standalone plugins for the modules that are currently part of the Performance Lab plugin, and then removing the corresponding modules from the PL plugin in favor of the new standalone plugins.
Milestones
This effort should be broken down into 2 milestones:
The first milestone will unblock the more urgent goal of having standalone plugins for every performance feature project, as well as therefore having a clear path forward also for new features.
The second milestone will ensure those standalone plugins are the canonical way to test those features, with the Performance Lab plugin still providing supporting features e.g. related to performance measurement and management of the performance related features and their plugins.
While the first milestone does not change anything notable for existing Performance Lab plugin users, the second one will require administrators to install/activate the new plugins and can therefore be considered a breaking change. As such, the second milestone should eventually be released with a major version number change, as
3.0.0.List of issues
The list below includes all related issues, somewhat ordered by their intended sequence of execution. Important to note:
Milestone 1
load.phpfiles #667Migrate SQLite integration plugin back into monorepo for development #661Milestone 2
2a (2.8.0 release)
feature/creating-standalone-pluginsfeature branch intotrunk#901Follow-up PRs:
2b (3.0.0 release)
pluginsfolder for standalone plugins #9342c (3.0.0 release polishing)
Follow-up Issues & PRs:
phpcs.xml.distFiles for Each Plugin to Isolate Text Domains #997pluginsdirectory plugin. #1006auto-sizesto plugins folder #972feature/auto-sizesbranch #971TODOfromdeploy-standalone-plugins.yml#1020get-plugin-dircommand for plugins #1026See #911 for somewhat related discussion, which however is not a blocker to this effort. Additionally, documentation for how to write a module will need to be updated after the 2b changes, and basic documentation for how to start a new plugin in the repo should be added too.