WordPress plugin developers: How do you find users to test…
0 reactions
WordPress plugin developers: How do you find users to test a breaking change in an upcoming release?
I have a plugin with \~10,000 active installations. It's ancient and simple; it only stores a value in a \`post\_meta\` field.
The current version is v2.2.1, but I've been working on a complete overhaul for a while, which I consider done. However, I can't ship it until I hear from as many users as possible that everything works as expected and, most importantly, nothing breaks or gets deleted.
A user who knows \`wp-cli\` could do this in a few minutes: \`wp db export\` (back up the database), then upload the \`.zip\` to the plugin directory and play around, both in the admin UI and a little bit with the code (I tried to keep it simple for laymen while making it more flexible for developers).
So, back to the question: How do you find users to test a new version (\`v3.0.0\`) of your plugin? Simply committing it seems reckless to me, despite the hours I put in to check everything.
#technology #dev #programming
I have a plugin with \~10,000 active installations. It's ancient and simple; it only stores a value in a \`post\_meta\` field.
The current version is v2.2.1, but I've been working on a complete overhaul for a while, which I consider done. However, I can't ship it until I hear from as many users as possible that everything works as expected and, most importantly, nothing breaks or gets deleted.
A user who knows \`wp-cli\` could do this in a few minutes: \`wp db export\` (back up the database), then upload the \`.zip\` to the plugin directory and play around, both in the admin UI and a little bit with the code (I tried to keep it simple for laymen while making it more flexible for developers).
So, back to the question: How do you find users to test a new version (\`v3.0.0\`) of your plugin? Simply committing it seems reckless to me, despite the hours I put in to check everything.
#technology #dev #programming
| 2,000 mlx | |
| 2 | |
| 0 |