The UpgradeActions page (https://flexget.com/UpgradeActions) page has incorrect information on it related to semantic versioning (semver).
Starting from version 2.0.0 we are using semantic versioning, in the form that any increase in the second digit means that configuration is not necessarily backwards compatible and may need to be updated.
The only public API to FlexGet is the configuration file. (While the WebUI may use an API, because the WebUI is developed in concert with FlexGet, that would not be a public API)
If you're making backwards-incompatible changes to the public interface with each minor version, as that page says, you're not following semantic versioning.
From SemVer.org (emphasis mine)
7) Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backwards compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code...
8) Major version X (X.y.z | X > 0) MUST be incremented if any backwards incompatible changes are introduced to the public API...
IMO, the resolution is to chose one of the following...
1) do real semantic versioning, meaning you'll be upgrading the major number a lot
2) reduce the number of incompatible changes that are made
3) stop claiming to be using semver and explicitly describe the version scheme you're using
So my question is where do I report this? It's not exactly a bug in the code, but it's not something I should just arbitrarily change on the wiki because it's connected to how code is versioned. Who should correct this (either process or documentation)?