4 ms·
This announcement post specifically addresses this: v0.1.0 introduces a new versioning policy [0], where patch versions (v0.1.1) are guaranteed to no longer bre
by lolinder 3y ago
This announcement post specifically addresses this: v0.1.0 introduces a new versioning policy [0], where patch versions (v0.1.1) are guaranteed to no longer break "stable" features, while minor versions (v0.2.0) can. At some point I'd assume they plan on stabilizing it such that even minor versions don't break stable features, but as a sibling notes, using v0 as a project's major version is usually intended to communicate that you shouldn't count on things staying stable.
[0] https://astral.sh/blog/ruff-v0.1.0#ruffs-versioning-policy https://astral.sh/blog/ruff-v0.1.0#ruffs-versioning-policy
- kstrauser 3y agoYep. Again, I’m not complaining. It broke a thing I use, so I fixed the thing. However, it’s something that pretty much all Ruff users to know about. Some projects look at their big x.y.Z number and decide to bump y or x to say “hey, it’s been long enough, let’s call it a new version”. This isn’t one of those cases.
- appplication 3y agoI can’t overstate how much I agree with the Ruff team in not being afraid to break things at this point. They have a very promising new tool, but it is very early. They are still very much learning the space and best way to produce their product. It would be an absolute tragedy if they felt compelled to maintain backwards compatibility for philosophical reasons at this stage, if they felt it constrained the capability or usability of their product.