It appears that all the development effort lately is in the Amazon stuff and Cloud computing stuff, which is all great and all, but Virtualmin is looking a bit tired.
Fess up, is Virtualmin a retired product?
Definitely not.
Virtualmin has been having regular releases about once a month, or more often, for years. Nothing has changed. New releases are being rolled regularly, bugs are being fixed, new features are being added. Documentation is being updated and written at a steady clip. API capabilities have been expanded in interesting ways.
But, you’re asking about the Virtualmin software repository for CentOS, which is not entirely the same thing as Virtualmin. 
Generally speaking, we try not to upgrade packages without good reason. But, ClamAV has been at the latest version on CentOS 5/i386 for several weeks…but the x86_64 version, for some reason, won’t build for me without having weird conflicting dependencies…I’m kinda stumped on why it’s happening. Building on CentOS 4 is proving to be quite ornery, as well. I got a bit distracted by the Ubuntu 10.04 LTS release, which took longer than usual, so I haven’t had as much time for CentOS 5 maintenance.
PHP, I’ll bump up to the latest 5.2 release soon. I’m hesitant to go to 5.3, as it breaks compatibility in a few ways that would cause some of our install scripts to break.
And Apache? MySQL? I haven’t individually checked them, but are they getting equally far behind?
In this case, you’ve misunderstood our packaging policy.
First up, we don’t replace MySQL. We have no control over the MySQL version on your system…it is whatever your OS provides.
And for Apache, in the cases where we do replace it, we replace it with the same version provided by the OS. This is a feature not a bug.
In short, we don’t have any desire to make major changes to your OS. You chose it, you must have had a reason to do so. So, we don’t mess with that choice. Again, this is a feature, not a bug.
We do happen to provide ClamAV for CentOS, just because it isn’t provided by the OS. And we do happen to provide a PHP version in the bleeding edge repo because we needed a slightly newer version to be available for folks to use a couple of the Install Scripts. I’m still a little uncomfortable about replacing any packages…but, people kept asking, so I went against my better judgement and added the bleeding edge repo.
Anyway, our policy has generally always been to stay out of the operating system business. You choose your OS, and we’ll work with that choice, rather than replacing a bunch of stuff.
