When I'm trying to choose plugins, I think it would be nice if I could see the release date directly on the list, and not having to go on the changelog to see such information.
I would not install a plugin that has not been updated in a long time, which for some plugins might be years.
On the plugins page on the website, we get the version and the compatible version of Openfire, but we don’t get the release date either.
I believe this information is helpful in the decision process for admins and it’s just more practical to have it on the first page.
What if plugin already does what it should and there is no new features needed or fixes? emailOnAway still works and there were no need to release a new version. There are also plugins with very recent release date, but having bugs. E.g. a few plugins didn't work after 4.3.0 release and they had to be fixed, although they release date was fairly recent (1-2 months). I don't think release date is a very useful indication.
I guess the best case would be to have it like in wordpress plugins pages, where its indicated what version it was tested with, and it still shows when it was last updated.
I figured it would be easier to just show the release date than to show if it was tested with the latest version or not. the release date is already there anyway.
We recently had similar discussion in the forums https://discourse.igniterealtime.org/t/indicate-openfire-version-compatibility/84503/6 testing all plugins for every release is not feasible with current resources.
I'm not categorically objecting showing the release date. As you said, it is there and it is shown on the site on every plugin's archive page. Though it will take more space to have this column in Admin Console and I'm not sure if we should emphasize this. You say you are not comfortable with old plugins. But they should work if they are in the list or should be fixed or removed. So seeing old release date of a perfectly working plugin one can start doubting, then go to forums and chat and start asking is it really working and someone will have to spend time encouraging and explaining 😀
Despite 's objection, which I didn't notice, I've merged the PR that add a release date to the Admin Console's list of plugins.
We can revert this change if it turns out to cause more trouble than it's worth.