Results 340 comments of Bryce Mecum

One of the tests this PR adds, in conjunction with the minimum supported C++ version check, caught a segfault in Arrow C++ that wasn't fixed until Arrow 15. I think...

It wasn't easy to expose the writer's `closed_` state to the R package for Arrow C++ 13/14 so I opted just to skip the test on Arrow C++

Hrm, maybe. I think the only thing to do other than that would be to duplicate the open/closed state tracking on the R side until we bump the minimum version...

Okay @jonkeane, I've bumped the minimum version from 13 to 15 and updated the PR body. There was only one `ARROW_VERSION_MAJOR` guard to be removed which I removed.

My fault for missing that. I changed that and added a NEWS.md entry while I was at it.

I think CI is happy now that I pushed https://github.com/apache/arrow/pull/42241/commits/c2d39d0dff6fa3f14389352b6436e94d7affa73c.

I'm pinging a few folks I think it would be good to get feedback from: @pitrou, @jorisvandenbossche, @zeroshade, @lidavidm. Anyone else is also encouraged to chime in too.

Yes, it should also hold for FlightServer, @nph. Do you have a use case where it'd be useful to have a similar check in FlightServer?