Closed raulcd closed 6 months ago
@jorisvandenbossche @kou should we add a release blog post for the release? Do we want to expand the issues that have been solved or should we just point to the changelog (as there aren't that many issues there): https://arrow.apache.org/release/14.0.2.html#changelog
Which issue did trigger 14.0.2? How about just mentioning it explicitly in the blog post?
Given it's relatively short, the changelog might be sufficient? (although not all PR titles are very descriptive ..) I can also make a human summary of the fixes later today if that is preferred.
This would be something like the following (I haven't checked all [R] labeled issues in detail, I am not sure if there is anything worth mentioning, or whether they are mostly CI fixes xx @assignUser)
Python:
C++:
Parquet (C++):
Thanks @jorisvandenbossche I've pushed a commit with the suggested notes: e4207732a156c3df0ce85ac6e646b7ebf3bff599
Sorry for the late reply, most/all changes for arrow R where fixes for 14.0.0 build system refactor related issues. I can open a PR in a bit (on PTO for now)
Release blog post for 14.0.2