raulcd commented on code in PR #525:
URL: https://github.com/apache/arrow-site/pull/525#discussion_r1612020456
##########
_posts/2024-05-27-nanoarrow-0.5.0-release.md:
##########
@@ -0,0 +1,203 @@
+---
+layout: post
+title: "Apache Arrow nanoarrow 0.4.0 Release"
+date: "2024-01-27 00:00:00"
+author: pmc
+categories: [release]
+---
+<!--
+{% comment %}
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements. See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to you under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License. You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+{% endcomment %}
+-->
+
+The Apache Arrow team is pleased to announce the 0.5.0 release of
+Apache Arrow nanoarrow. This release covers 79 resolved issues from
+9 contributors.
+
+## Release Highlights
+
+The primary focus of the nanoarrow 0.5.0 release was expanding the
+initial [Python bindings](#python-bindings) that were released in 0.4.0.
+The nanoarrow Python package can now create and consume most Arrow
+data types, arrays, and array streams, including conversion to/from
+objects compatible with the Python buffer protocol and conversion
+to/from lists of Python objects.
+
+The nanoarrow 0.5.0 release also includes updates to its build
+configuration to make it possible to use nanoarrow with `FetchContent`
+in projects with a wider variety of CMake usage. In addition to CMake,
+nanoarrow now supports the Meson build system. Thanks to
+[@vyasr](https://github.com/vyasr) and [@WillAyd](https://github.com/WillAyd)
+for contributing these changes!
+
+In the [R bindings](#python-bindings), support for reading IPC streams
+is now accessible with `read_nanoarrow()`!
+
+Finally, helpers to reconcile modern C++ usage with nanorrow C
+structures (e.g., iterating over an `ArrowArrayStream` or
+`ArrowArray` using a range-for loop) were added to `nanoarrow.hpp`.
+Thanks to [@bkeitz](https://github.com/bkietz) for contributing these
+changes!
+
+See the
+[Changelog](https://github.com/apache/arrow-nanoarrow/blob/apache-arrow-nanoarrow-0.5.0/CHANGELOG.md)
+for a detailed list of contributions to this release.
+
+## Breaking Changes
+
+Most changes included in the nanoarrow 0.5.0 release will not break most
downstream
+code; however, several changes in the C library are breaking changes to
previous
+behaviour.
+
+- `ArrowBufferResize()` and `ArrowBitmapResize()` now adjust `size_bytes`/
+ `size_bits` in addition to `capacity_bytes`/`buffer.capacity_bytes`.
+ Preivously these functions only adjusted the capacity of the underlying
+ buffer which caused some understandable confusion even though this
+ behaviour was documented. This change affects all usage of
+ `ArrowBufferReisze()` and `ArrowBitmapResize()` that *increased* the size
+ of the underlying buffer (i.e., usage where `shrink_to_fit` was non zero
+ should be unaffected).
+- `ArrowBufferReset()` now *always* calls the allocator's `free()` callback.
+ Previously, a call to the `free()` callback was skipped if the pointer was
+ `NULL`; however, this led to some confusion and made it easy to accidentally
+ leak a custom deallocator whose pointer happened to be `NULL`.
+- As a consequence of the above, it is now mandatory to call
`ArrowBufferInit()`
+ before calling `ArrowBufferReset()`. There was some existing usage of
nanoarrow
+ that zero-ed the memory for an `ArrowBuffer` and then (sometimes) called
+ `ArrowBufferReset()`. Preivously this was a no-op; however, after 0.5.0 this
+ will crash. This is consistent with other structures in the nanoarrow C
library
+ (which require an initialization before it is safe to reset/release them).
+
+
+### Python bindings
+
+The nanoarrow Python bindings are distributed as the `nanoarrow` package on
+[PyPI](https://pypi.org/) and [conda-forge](https://conda-forge.org/):
Review Comment:
Should we point to the actual project?
```suggestion
[PyPI](https://pypi.org/project/nanoarrow/) and
[conda-forge](https://anaconda.org/conda-forge/nanoarrow):
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
