yes you do post in News !! And we appreciate all your work !!! (and the other staff too !!)
but I hope you can see our … nervousness … when we see something like 2.100 (or 2.101) being announced in News but don’t know if its yet been vetted for the Virtualmin environment
It would really help if either:
you do cross post when it has been vetted for Virtualmin usage
or
the News posting explicitly says its ready for Virtualmin (or not yet ready)
that way we don’t (at least in a Redhat/Centos/etc environ) have to keep doing a
yum list webmin
against the virtualmin-universal repo to check and check and check again
my point was — a little extra work on your part (yes I know that sounds uncaring) means much less work (in total) for all of us – as we will know when webmin is OK to upgrade in a Virtualmin environment.
I added it to the Virtualmin repos (where we only release vetted software intended for Virtualmin users to install), and I posted an announcement and change logs to the News section, as I always do. This is how we release updates for Virtualmin. If you don’t believe me that we believe it’s ready for Virtualmin when I put it in the Virtualmin repos, I don’t know what else to do.
If it is in the Virtualmin repos, you should update to it. I’m not going to send out engraved invitations.