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 v23.06 Schedule

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

Phase Start End Duration
Development (cuDF/RMM/rapids-cmake/cugraph-ops/raft) Thu, Mar 23 Wed, May 17 40 days
Development (others) Thu, Mar 30 Wed, May 24 40 days
Burn Down(cuDF/RMM/rapids-cmake/cugraph-ops/raft) Thu, May 18 Wed, May 24 5 days
Burn Down (others) Thu, May 25 Wed, May 31 4 days
Code Freeze/Testing (cuDF/RMM/rapids-cmake/cugraph-ops/raft) Thu, May 25 Tue, Jun 6 9 days
Code Freeze/Testing (others) 1 Thu, Jun 1 Tue, Jun 6 4 days
Release Wed, Jun 7 Thu, Jun 8 2 days

PROPOSED Release v23.08 Schedule

Phase Start End Duration
Development (cuDF/RMM/rapids-cmake/cugraph-ops/raft) Thu, May 18 Wed, Jul 19 40 days
Development (others) Thu, May 25 Wed, Jul 26 40 days
Burn Down(cuDF/RMM/rapids-cmake/cugraph-ops/raft) Thu, Jul 20 Wed, Jul 26 5 days
Burn Down (others) Thu, Jul 27 Wed, Aug 2 5 days
Code Freeze/Testing (cuDF/RMM/rapids-cmake/cugraph-ops/raft) Thu, Jul 27 Tue, Aug 8 9 days
Code Freeze/Testing (others) 1 Thu, Aug 3 Tue, Aug 8 4 days
Release Wed, Aug 9 Thu, Aug 10 2 days
  1. Cross-library dependencies are pinned during this time-frame. For example: Dask and Distributed.  2


Table of contents