Vladimir, I proposed a straw poll to try to move this thread from a shouting match to a productive conversation. Straw polls are an imperfect mechanism but can sometimes be helpful. It's too bad you didn't find it helpful. I did and I hope others did.
> Suppose PR verification passes. > Suppose I merge the PR. > Then "post-merge CI job fails". > Who resolves the issue? > In the proposal, there is no issue with the post-merge CI job failing. It's simply the fyi: "the Avatica upgrade is going to be more than a version change". Everybody can ignore it. > I'm strongly against moving the burden of such maintenance to committers. > The newly added code should not contain known bugs. > There is no burden in this proposal beyond changing the CI. From the Calcite codebase's perspective, Calcite could stay on an old Avatica release forever. This is no different than any other library Calcite sources: if someone wants to upgrade the version of any library that Calcite depends on, they are responsible for solving any incompatibilities before pointing at the new version. The survey is biased, so are the outcomes. > :D On the one hand, all surveys are biased unless there is substantial rigor during construction. On the other hand, I doubt you're referencing the general weakness of simple surveys. I think you're questioning my underlying motivation. In that you're seeing something that isn't there. I have zero opinion on whether to merge or not (and didn't respond to the survey). > Why don't you ask the other questions raised in the thread? > The longer the survey, the less responses one expects to get. The survey was probably already too long given that we only got 7 responses.
