Virtualmin virtual-server module version 4.00 released

Howdy all,

I’ve just rolled out version 4.00 of Virtualmin virtual-server module. This is a mostly bugfix release.

Changes since 3.99:

  • Updated the Django script installer to version 1.5.1, SugarCRM to 6.5.12, Mediawiki to 1.20.4 and 1.19.5, PiWik to 1.11.1, Drupal to 7.22, phpScheduleIt to 2.4.1, Moodle to 2.4.3, Typo3 to 4.6.18, phpScheduleIt to 2.4.1, FengOffice to, Dolibarr to 3.3.1, Gallery to 3.0.7, TikiWiki to 10.2, CMS Made Simple to 1.11.6, RoundCube to 0.9.0, Nucleus to 3.65, phpMyAdmin to, Mantis to 1.2.15, phpPgAdmin to 5.1, FosWiki to 1.1.8, Joomla to 3.1.0, and ZenPhoto to version
  • If Webmin’s BIND module is configured to use the SPF type for Sender Permitted From records, Virtualmin will create both SPF and TXT records for domains.
  • Added a field to the DKIM page for entering domains to exclude from signing and DNS record creation.
  • Added buttons to the Scheduled Backups page to enable or disable backups, and a button on the Edit Scheduled Backup page to clone a backup configuration.

As always, if you run into any issues, let us know in the ticket tracker.

Hi there!

I think it would be wonderful to introduce Semantic Versioning ( ) on Virtualmin. Changing the major version nomber (3.99 --> 4) for a minor bugfix release is somewhat confusing.

Anyway, thank you for the development!

I agree, I saw version 4.00 in the updates list and was expecting a large release with possible compatibility problems so was hesitant to update in case anything broke.

Awesome product though - keep up the good work :slight_smile:

Also, why not phpMyAdmin 4.x ? (EDIT: I see 4.02 is available, but you’re also maintaining support for older versions, excellent stuff)

We don’t, historically, do “major upgrades”, we do very frequent small updates. This is to avoid the pain of big changes…we didn’t go to 4.00 to cause confusion or to indicate big changes, we did it because we were out of numbers without adding another digit (3.99 was the prior release)! I’m not sure if semantic versions makes sense when every new release is a small set of improvements over the last version, and new releases happen so frequently (every month or two, usually).

We try really hard not to introduce incompatible changes, regardless of version numbers, and when we do we document those changes.

We’d like to get past worrying about versions and just know that everyone is running the latest, kinda the way Chrome and Firefox do things now. I don’t know what version of either I’m running without looking, but I know I’m running the latest version because there’s no update notification. Same mindset ought to be possible with Virtualmin.

That said, we may end up breaking some kinds of compatibility in Webmin, if we introduce a version 2.0 (which has been in discussion for a while now, in order to shed some technical debt in the 15 year old codebase). But, it’s unlikely to effect most Virtualmin users in a major way, and it would be several months or a year in the future.

Chrome use something very similar to SemVer -

With SemVer you wouldn’t run out of numbers as you could have gone from 3.99 to 3.100 (or 3.0.99 to 3.0.100 as it would more likely be).

If you do release a ‘Version 2.0’ - surely it will have to be called something else, as I assume you’ve already had a version 2.0!

Anyway - keep up the great work, however you decide to version it :slight_smile: