I have a bunch of colleagues like this. If they were left to their ways we’d still be using unpatched frameworks from 20 years ago. I find it pretty frustrating.
Bold of you to assume they’ll update to the next major release. Attempts update, breaks the build…rollback! We’re locking the release to this specific version now.
I have lived this comment and the fix was like updating a few dependencies and some configs…it took ten minutes. They were on some deprecated version for years…
Ahh… the ostrich approach
I have a bunch of colleagues like this. If they were left to their ways we’d still be using unpatched frameworks from 20 years ago. I find it pretty frustrating.
Same. “If the warning doesn’t break the build, just ignore it,” (even if it literally says it’s going to break the build in the next major release)
Bold of you to assume they’ll update to the next major release. Attempts update, breaks the build…rollback! We’re locking the release to this specific version now.
I have lived this comment and the fix was like updating a few dependencies and some configs…it took ten minutes. They were on some deprecated version for years…
Edit cause typo/autocorrect