6.0 release blog post

[amol-]

No description provided.

[github-actions]

Thanks for opening a pull request!

Could you open an issue for this pull request on JIRA?
https://issues.apache.org/jira/browse/ARROW

Then could you also rename pull request title in the following format?

ARROW-${JIRA_ID}: [${COMPONENT}] ${SUMMARY}

See also:

• Other pull requests
• Contribution Guidelines - How to contribute patches

[nealrichardson]

@alamb should we integrate this changelog with the one the main release process generates (e.g. https://arrow.apache.org/release/5.0.0.html)? (cc @thisisnic @kszucs)

[alamb]

If you can that would be great. The changelog generation process for rust is fairly primitive at the moment

[mrkn]

Thank you for reminding me. I’ve already created the content of my part. I can submit my part tonight after my child go to bed.

On Wed, Nov 3, 2021 at 17:51 Alessandro Molina ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In _posts/2021-10-22-6.0.0-release.md <#153 (comment)>: > +* Many new `pyarrow.compute` functions are available (see the C++ notes above for more details), and introspection of the functions was improved so that they look more like standard Python functions. +* All Python functions and classes should now have documented parameters in the API reference. +* SIMD optimization is now enabled in M1 wheels +* Wheels are now built for more Python versions on M1 systems. +* PyArrow is now compatible with Python 3.10 +* Creating Arrow arrays now supports more than just numpy arrays as masks +* Printing Tables now previews the values in the columns +* `copy_files` is now available in Python +* Datasets now support ORC files +* Sets are now supported when building arrays or converting from pandas. +* 39 bugs have been fixed. + +## R notes + +## Ruby and C GLib notes + @mrkn <https://github.com/mrkn> friendly reminder to update the Ruby release notes as I think it's the last part pending for the blog post to be complete :) — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#153 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAA65655QJFRA7PR7TKO63UKDZ27ANCNFSM5F7C5XGQ> .

-- Kenta Murata, sent from Gmail Mobile