@baris yes, this was our method; however, there have been many real new users who wanted to use those fields, and it was taking a lot of time for us to fill in their info manually, so we had to abandon this method.
It would be quite helpful if the plugins that were available for download from the admin panel were required to indicate the NodeBB version they were compatible with, a date of when it was last updated, or things of that nature so that quickly at a glance you can see if something is older or not compatible anymore as simply having the plugins current version is not that helpful with nothing to compare that against.
@julian I followed the docs. I got an outdated version labeled 0.4.3. No one ever told me to update the themes. It really does not matter if everything worked fine for a long time. This should just show you that you need more testing. You obviously did not test installing version 0.4.3 as described in the docs directly.
I know it's not easy to find bugs, but please seriously consider this request as it will prevent a lot of headaches in the future and show admins what might not be working. I cannot make a good bug report if I am using outdated software. I did not even know that it was outdated. You won't be able to solve future bugs if people use outdated software without knowing.
BTW.: as I already wrote on github, renaming the branches won't help anyone if it contains outdated software or the docs are insufficient. I would be really glad to see my request beingf implemented and help thousands of people setting up a very nice forum.
Compatibility notes should be standard in all plugins, but it's still early. We're moving from minver to compatibility, so that should cover all cases, and allow the package manager to show only plugins approved for installation.