danepitkin commented on code in PR #469:
URL: https://github.com/apache/arrow-site/pull/469#discussion_r1475082965
##########
_posts/2024-01-29-nanoarrow-0.4.0-release.md:
##########
@@ -0,0 +1,224 @@
+---
+layout: post
+title: "Apache Arrow nanoarrow 0.4.0 Release"
+date: "2024-01-29 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.4.0 release of
+Apache Arrow nanoarrow. This release covers 46 resolved issues from
+5 contributors.
+
+## Release Highlights
+
+The primary focus of the nanoarrow 0.4.0 release was testing, stability, and
code
+quality. Notably, an implementation of the
+[C data interface integration
test](https://arrow.apache.org/docs/format/Integration.html#example-c-data-interface)
+protocol was added to ensure data produced or consumed by nanoarrow can be
+consumed or produced by other Arrow implementations.
+
+Apache Arrow nanoarrow 0.4.0 also contains experimental [Python
bindings](#python-bindings)
+to the C library for the purposes of community testing and feedback while a
more stable
+set of bindings is prepared (targeted for 0.5.0).
+
+See the
+[Changelog](https://github.com/apache/arrow-nanoarrow/blob/apache-arrow-nanoarrow-0.4.0/CHANGELOG.md)
+for a detailed list of contributions to this release.
+
+## Breaking Changes
+
+Changes included in the nanoarrow 0.4.0 release will not break most downstream
+code; however, several changes in the C library may result in additional
compiler
+warnings that could cause downstream build failures for projects with strict
+compiler warning policies.
+
+First, in debug mode (i.e., when `NANOARROW_DEBUG` is defined), an ignored
return
+value for functions that return `ArrowErrorCode` now issues a compiler warning
+for compilers that support an "unused result" attribute. Ignoring the return
value
+of these functions is a common error and return values that are not
+equal to `NANOARROW_OK` should be propagated as soon as possible. The C library
+provides tools to check return values in a readable way. Notably:
+
+- `NANOARROW_RETURN_NOT_OK()` can be used in a wrapper function that also
returns
+ `ArrowErrorCode`.
+- `NANOARROW_THROW_NOT_OK()` can be used from C++ code that inclues
`nanoarrow.hpp`
+ and is prepared to handle exceptions.
+- `NANOARROW_ASSERT_OK()` can be used to to check for `NANOARROW_OK` only in
+ debug mode (i.e., silently ignore errors in release mode and will crash in
+ debug mode with a message indicating the location of the error).
+
+Of these, the first or second is preferred. The
+[Getting Started with nanoarrow in C/C++
tutorial](https://arrow.apache.org/nanoarrow/main/getting-started/cpp.html#arrow-c-data-nanoarrow-interface-basics)
+includes examples and advice for handling errors eminating from the nanoarrow C
Review Comment:
```suggestion
includes examples and advice for handling errors emanating from the
nanoarrow C
```
--
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]
