Major vs. Minor Updates

[dream-encode]

I don't see it discussed previously, so I thought I'd throw this out there. Has any consideration been given to allow for more ganularity on the auto-update flag?

In other words, instead of just having "Enabled" and "Disabled", adding "Enabled for Minor Versions Only" and changing "Enabled" to "Enabled for All Versions".

If this is potential plugin territory, can hooks be added to parse the version when deciding whether a plugin/theme is auto-updated?

[pedro-mendonca]

That might be interesting, as it works in core, the problem is that plugin authors use different version numbering, there is no rule for that so it can be relied upon.

[desrosj]

Ya, I agree with @pedro-mendonca. Unfortunately, I don't think this is possible currently because there is no guarantee that all plugin or theme authors abide by the same rules for versioning. Authors are free to version how they wish. In core, the versions are defined and controlled.

Ideally, I think, there would be enabled, disabled, security, minor, major. But that would require changes to the plugin directory guidelines and a lot of outreach/effort.

[desrosj]

As for plugin territory, this should be doable with the filters that are currently in trunk. If that's not the case, feel free to request some new ones!

[pbiron]

This has been discussed in #4.