GitHub user parshimers added a comment to the discussion: Policy and guidance on upgrades and backwards-compatibility between versions
Agreed. I think it is an exceptional case, and what made me want to start this discussion. You can always weasel out a bit on the "should" being there, but it's best to avoid that. I think a lemma to this policy is that we should ensure all of our downstream dependencies have compatible guarantees with this one. The MinIO situation is a consequence of an incompatible guarantee: it was entirely unsupported, and in fact the original authors had a demonstrated desire to kill the product as it existed originally. My proposal would be that we should ensure that at the very least, what we release has no deprecated or unsupported dependencies at the time of the release. If we really need them, then we should vendor them in and maintain them ourselves. If at any time the dependency becomes unsupported, we (hopefully with some warning) announce that it's the end of the line for that version. GitHub link: https://github.com/apache/texera/discussions/8570#discussioncomment-18486076 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
