So Diesel 2.0 is a thing that is happening this year, and I'm debating whether I should write a blog post about it. None of the planned changes are likely to affect most users (and we have the same "easy migration" standards we have for deprecations. 1/
At the same time I'm worried about the optics of having a 2.0 at all. It's been just over a year since 1.0 (probably 18 months when 2.0 ships). I want to make sure folks can see this is because of our commitment to semver, not because we plan on breaking stuff annually.
-
-
It's also unfortunate that we're going to force a lot of libraries to do a new release with `diesel = ">= 1.0, < 3.0"` but that's unavoidable since these changes might actually break libraries
Show this thread -
I guess at the end of the day this is what some of the anti-semver folks complain about. I don't expect this to affect 99% of our users. But I do expect it to break *some* folks (especially libraries), so I think it's important to communicate that in our versioning
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.