Backwards compatibility

[AndrolGenhald]

Can we define somewhere what guarantees we want to provide across minor and major versions? It seems to me that we provide very few guarantees for end-users, but we want to make sure plugins will continue to work until a major version change.

If major versions only matter for plugins, I'm thinking the installation docs should be changed to composer require --dev vimeo/psalm="*" so that the latest version of psalm is used based on plugin support, otherwise composer defaults to the current major version which means a lot of users may not automatically upgrade to psalm 5 once it's released.

[AndrolGenhald]

I suppose for end users removing annotations between major versions might break things, which might be a good enough reason to default to requiring the current major version.

[orklah]

Well, my opinion is that most people should pin Psalm in a specific version to avoid breaking their build on new versions of Psalm (even bugfixes).

Then it should be updated on occasion.

So yeah, BC break is mainly code related, so it impacts plugins first