This is an automated email from the ASF dual-hosted git repository.

lidavidm pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/arrow-adbc.git


The following commit(s) were added to refs/heads/main by this push:
     new 1b8970cef docs: update drivers list (#4897)
1b8970cef is described below

commit 1b8970cef3e704e1a53b3356e7edd39b8b855e04
Author: David Li <[email protected]>
AuthorDate: Thu Oct 15 16:05:37 2026 -0700

    docs: update drivers list (#4897)
---
 docs/source/development/releasing.rst |  8 +++++---
 docs/source/driver/index.rst          | 12 ++++++++++++
 2 files changed, 17 insertions(+), 3 deletions(-)

diff --git a/docs/source/development/releasing.rst 
b/docs/source/development/releasing.rst
index 9b65e604b..b8e22695d 100644
--- a/docs/source/development/releasing.rst
+++ b/docs/source/development/releasing.rst
@@ -72,7 +72,9 @@ Before creating a Release Candidate
 
 1. Regenerate the LICENSE.txt (see CONTRIBUTING.md and ci/licenses/README.md) 
and create a pull request if any changes were needed. Generally, only the 
license for Go-based drivers will need to be regenerated.
 
-2. Set up your shell environment:
+2. Update the list of ADBC drivers in the documentation (:ref:`driver-table`), 
ensuring drivers from third parties are represented (e.g. from the ADBC Driver 
Foundry).
+
+3. Set up your shell environment:
 
    .. code-block::
 
@@ -82,13 +84,13 @@ Before creating a Release Candidate
       # Activate conda environment
       mamba activate adbc
 
-3. Ensure merged pull requests and closed issues have their milestone set 
appropriately:
+4. Ensure merged pull requests and closed issues have their milestone set 
appropriately:
 
    .. code-block::
 
       ./dev/release/assign-milestone.sh
 
-4. Create a fresh clone of the latest apache/arrow repo, which is used by 
several steps below.
+5. Create a fresh clone of the latest apache/arrow repo, which is used by 
several steps below.
 
    .. warning:: Make sure an up-to-date clone is used, so that the Linux 
packaging scripts in particular are in sync, else there is the possibility of 
corrupting the shared Linux package repositories.
 
diff --git a/docs/source/driver/index.rst b/docs/source/driver/index.rst
index f8f003778..7458f5655 100644
--- a/docs/source/driver/index.rst
+++ b/docs/source/driver/index.rst
@@ -55,6 +55,10 @@ driver in the table below is packaged this way.
      - ``bigquery``
      - Foundry
      - :iconlink:`fa-brands 
fa-github|https://github.com/adbc-drivers/bigquery|GitHub repository`
+   * - `Apache Cassandra <https://adbc-drivers.org/drivers/cassandra/>`__
+     - ``cassandra``
+     - Foundry
+     - :iconlink:`fa-brands 
fa-github|https://github.com/adbc-drivers/cassandra|GitHub repository`
    * - `chDB <https://clickhouse.com/docs/chdb/install/adbc>`__
      - ``chdb``
      - Vendor
@@ -71,6 +75,10 @@ driver in the table below is packaged this way.
      - ``datafusion``
      - Foundry
      - :iconlink:`fa-brands 
fa-github|https://github.com/adbc-drivers/datafusion|GitHub repository`
+   * - `Apache Druid <https://adbc-drivers.org/drivers/druid/>`__
+     - ``druid``
+     - Foundry
+     - :iconlink:`fa-brands 
fa-github|https://github.com/adbc-drivers/druid|GitHub repository`
    * - :doc:`DuckDB <duckdb>` [#duckdb]_
      - ``duckdb``
      - Vendor
@@ -79,6 +87,10 @@ driver in the table below is packaged this way.
      - ``exasol``
      - Vendor
      - :iconlink:`fa-brands 
fa-github|https://github.com/exasol/adbc-driver-exasol|GitHub repository`
+   * - `Firebolt <https://adbc-drivers.org/drivers/firebolt/>`__
+     - ``firebolt``
+     - Foundry
+     - :iconlink:`fa-brands 
fa-github|https://github.com/adbc-drivers/firebolt|GitHub repository`
    * - :doc:`Apache Arrow Flight SQL <flight_sql>` [#compat-flightsql]_
      - ``flightsql``
      - ASF

Reply via email to