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
Firstly, thank you for contributing to the Grafana plugin ecosystem.
I'm reaching out as this plugin is at risk of being deprecated from the Grafana plugin catalog as it depends on Angular, which is deprecated and support for which is about to end.
We recognise that priorities change and that it may no longer be possible to keep plugins up to date. For your awareness, deprecation has no impact on existing users of the plugin, but discourages further adoption to prevent users from starting to rely on a component which won't receive updates.
Please advise if you have plans to update this plugin, or alternatively that you agree the plugin should be deprecated. In the case of the latter, if there is any specific guidance you would like to offer users of the plugin - please let me know and we can include this in the deprecation notice.
Feel free to email me at [email protected] if preferred; apologies, we don't have an email address associated with this plugin so I had to raise an issue.
If we don't hear from you within 30 days, I'll go ahead and deprecate the plugin.
Thank you again
David
The text was updated successfully, but these errors were encountered:
Hi there from Grafana Labs 👋
Firstly, thank you for contributing to the Grafana plugin ecosystem.
I'm reaching out as this plugin is at risk of being deprecated from the Grafana plugin catalog as it depends on Angular, which is deprecated and support for which is about to end.
We recognise that priorities change and that it may no longer be possible to keep plugins up to date. For your awareness, deprecation has no impact on existing users of the plugin, but discourages further adoption to prevent users from starting to rely on a component which won't receive updates.
Please advise if you have plans to update this plugin, or alternatively that you agree the plugin should be deprecated. In the case of the latter, if there is any specific guidance you would like to offer users of the plugin - please let me know and we can include this in the deprecation notice.
Feel free to email me at [email protected] if preferred; apologies, we don't have an email address associated with this plugin so I had to raise an issue.
If we don't hear from you within 30 days, I'll go ahead and deprecate the plugin.
Thank you again
David
The text was updated successfully, but these errors were encountered: