RAPIDS Maintainers Docs

RAPIDS projects use an established set of guidelines and procedures for all projects. These are available for the community to review and provide feedback on.

Intended audience

Developers

Project Leads

Operations

Release v26.02 Schedule

NOTE: Dates are subject to change at anytime. Completed release schedules are posted here.

Phase Start End Duration
Development (cuDF/RMM/rapids-cmake/raft/dask-cuda/KvikIO/ucxx/rapidsmpf) Thu, Nov 13, 2025 Wed, Jan 14, 2026 39 days
Development (others) Thu, Nov 20, 2025 Wed, Jan 21, 2026 39 days
Burn Down (cuDF/RMM/rapids-cmake/raft/dask-cuda/KvikIO/ucxx/rapidsmpf) Thu, Jan 15, 2026 Wed, Jan 21, 2026 5 days
Burn Down (others) Thu, Jan 22, 2026 Wed, Jan 28, 2026 5 days
Code Freeze/Testing (cuDF/RMM/rapids-cmake/raft/dask-cuda/KvikIO/ucxx/rapidsmpf) 1 Thu, Jan 22, 2026 Tue, Feb 3, 2026 9 days
Code Freeze/Testing (others) Thu, Jan 29, 2026 Tue, Feb 3, 2026 4 days
Release Wed, Feb 4, 2026 Thu, Feb 5, 2026 2 days

PROPOSED Release v Schedule

Phase Start End Duration
Development (cuDF/RMM/rapids-cmake/raft/dask-cuda/KvikIO/ucxx/rapidsmpf)     days
Development (others)     days
Burn Down (cuDF/RMM/rapids-cmake/raft/dask-cuda/KvikIO/ucxx/rapidsmpf)     days
Burn Down (others)     days
Code Freeze/Testing (cuDF/RMM/rapids-cmake/raft/dask-cuda/KvikIO/ucxx/rapidsmpf) 1     days
Code Freeze/Testing (others)     days
Release     days
  1. Cross-library dependencies are pinned during this time-frame. For example: Dask and Distributed.  2


Table of contents