6 ms·
Folks with an eye towards backwards compatibility typically don't implement breaking changes without a year of deprecation warnings emitted by the software. Co
by klyrs 6y ago
Folks with an eye towards backwards compatibility typically don't implement breaking changes without a year of deprecation warnings emitted by the software. Contrast that to a notice posted in a sub-basement 6 months before instituting a breaking change. The shock and alarm do seem warranted IMO.
- Twirrim 6y ago> project mailing lists, Github issue tracker, project IRC channel, documentation (changelog, FAQ), and Twitter channels It's hardly a notice posted in a sub-basement 6 months before instituting a breaking change. They communicated via numerous mechanisms.
- klyrs 6y agoIt's a sub-basement from the perspective of folks for whom this is a second-order dependency. And it sounds like there are many more of them than there are folks that caught wind of this. Regardless. The common practice is a year of emitting warnings from the software, that the end-user will see. That's prominent and allows package maintainers enough time to work around the upcoming breakage. Six months notice on a mailing list is simply not prominent enough, and it's half the standard year which puts undue strain downstream.
- deleted 6y ago[deleted]
- detaro 6y agoHow do you do a deprecation warning for a new language being a build dependency? What does it look like? "your build environment is being deprecated"?
- tom_mellior 6y agoIn C you can implement a "your build environment is being deprecated" message like this: #ifndef I_UNDERSTAND_THAT_SOON_RUST_WILL_BE_MANDATORY #error "Starting with version xxx this package will need Rust to compile. Recompile with -DI_UNDERSTAND_THAT_SOON_RUST_WILL_BE_MANDATORY to acknowledge that you understand this warning." #endif Anyone building from source would get notified in a way that's impossible to miss but easy to turn off.
- detaro 6y agoTrue, that's possible, but quite brutal and I'd expect that would merely have lead to shouting and people going wild over their builds breaking a year earlier.
- marcinzm 6y agoAnd thousands upon thousands of automated CI jobs and docker container builds fail. You're basically causing massive developer stress to anyone who automatically compiles your package. Most would consider that a bad tradeoff to help a tiny fraction of your users who'd be impacted and also refuse to follow your mailing list.
- naniwaduni 6y agoYou're going to do that a few versions down the line anyway. Why not ahead of time? The only downstreams this affects more are the ones who decide to suppress the warning for now and ... put it off until you release the change that actually required breakage.
- eyelidlessness 6y ago> And thousands upon thousands of automated CI jobs and docker container builds fail. You're basically causing massive developer stress to anyone who automatically compiles your package. This isn’t a major source of stress: you include migration instructions and even tooling to automate it. The thing that’s stressful is when your build fails with completely unexpected errors and no indication of what went wrong. Loudly announcing breaking changes is disruptive to some extent, but not doing so either means more disruption or nothing can ever change at all.
- setr 6y agoIsn't this basically equivalent to what they did? Their actual action was to include a dummy rust requirement just to break/warn people who wouldn't be prepared for it as an actual dependency.
- ohgodplsno 6y ago
- klyrs 6y agoYes. It's pretty simple to insert a stub module which is imported in a try/catch, where failure to load results in a warning.
- detaro 6y agoHm yeah, that sounds like a bit of a hassle to set up (have it build where possible but not fail the build), but otherwise an elegant solution, since it would pass cleanly for people that have a suitable environment.