You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current practice is that new plugins are not pushed before they have matured to a "stable" level.
Could it be beneficial to push development/prototype versions? This would make it easier for others to test and give feedback in the development process of a plugin instead of after or very late in the process.
There's obviously a risk with such an approach as protype plugins can be changed or removed without notice, so it would need some way of clearly letting end-users understand it's a prototype/dev version.
One suggestion could be to include "prototype" prefix in the plugin names. One could also add a warning text in the doc clearly stating this is a prototype that can be changed/removed at any time.
The text was updated successfully, but these errors were encountered:
Current practice is that new plugins are not pushed before they have matured to a "stable" level.
Could it be beneficial to push development/prototype versions? This would make it easier for others to test and give feedback in the development process of a plugin instead of after or very late in the process.
There's obviously a risk with such an approach as protype plugins can be changed or removed without notice, so it would need some way of clearly letting end-users understand it's a prototype/dev version.
One suggestion could be to include "prototype" prefix in the plugin names. One could also add a warning text in the doc clearly stating this is a prototype that can be changed/removed at any time.
The text was updated successfully, but these errors were encountered: