> On 09.05.2017, at 01:05, Fabien Crespel <
fab...@crespel.net> wrote:
>
> If they're fine, what should I do to get the plugin back to the Update Center? just release it as usual? (version will be 1.4.0)
File a PR for
https://github.com/jenkins-infra/backend-update-center2 doing basically the same as PR 134 but for your plugin:
- Remove from exclusions
- Adapt warnings regex to only match affected releases
>
> As a side note, when this kind of issue occurs I would appreciate to be notified by mail if possible... it took me 10 days to notice it and even longer to find the time to fix it :-(
Good point. As I explained in the related blog post, I was unable to contact everyone beforehand, and afterwards… TBH I didn't think it was necessary after emailing all the lists etc. I should have done a better job informing maintainers (in the case of maintained plugins). Sorry about that!