luceos I don't agree and I'm deluded by that but ok, maybe it's me that is not understanding.
I cannot upgrade to the new Flarum version because of extensions.
Flarum doesn't have security in the core so I need have extensions: captcha, stopforumspam, etc that I cannot avoid to have.
I cannot monitor or be notified when a new extension is released because there is no such check and feature inside extension manager on Flarum so I was opening an issue where issue are present and I'm not asking every hours or minute to implement compatibility, just alerting as I think is normal.
Closing issue when the issue is not resolved is confusing and I think is more wrong that open an issue when an issue is present and want just monitor for the resolution.
If I was able to have capacity to help and do extension compatible with the new version at this time i was already done pull requests but I don't understand how to do and I see is not easy. I'm not a programmer.
I don't think closing issue when issue are not resolved his good and I don't see nothing on bad reporting an issue when a components have issue. What is wrong, on my point of view is close an issue when is not resolved.
Anyway will try to monitor all extension that are incompatible. I cannot be there every day and check all Flarum discussion. Will try to subscrive to GitHub update alert.
I was trying to monitor when I will be able to upgrade but all issue has been closed so, I cannot do that. I can delete the repo I created for monitor the situation. I think this is not nice from your side with all my respect and understanding for the work you have to do.
Say that create issue for report and monitor an issue is not civil, I don't agree.