TCRL Release and Naming Updates

Overview

Key changes are being made to the Test Case Reference List (TCRL) release process to support timely access to updates and improve consistency across documentation. This Knowledge Base Article provides an overview of updates to the release frequency, cadence, and naming structure of TCRL packages. These modifications are intended to provide clearer versioning, more predictable release timing, and improved support for all stakeholders.

TCRL release frequency and cadence

To align with the increased Core Specification release cadence—now occurring twice per year—and to expedite the delivery of important fixes to members, the TCRL release cadence is changing. Moving forward, there will be 3–4 TCRL releases annually:

• One release will coincide with each Core Specification release
• One or two additional releases will focus on non-Core Specification material

This change aims to ensure faster access to updates and improved support across all relevant technologies.

TCRL package naming

We are also updating the TCRL document and package naming structure to better align with industry standards and enable flexibility in release timing. Starting after TCRL 2025-2, we will discontinue the year-based numbering (e.g., “2025-2”) and replace it with a simple, incrementing integer format. The release after 2025-2 will be named “pkg100.”

The image below illustrates how the updated release cadence will lead to a temporary overlap of three active TCRL packages and reflects the introduction of the new naming structure.

Within each package, rollup TCRLs (e.g., the Mesh TCRL) will use a publication-based numbering system (e.g., Mesh.TCRL.p14), with each rollup TCRL incrementing independently upon release. For comprehensive details, please refer to the Document Naming and Marking Document (DNMD), v7, which is expected to be updated with the new naming scheme in Q3.

(This KBA is intended to provide Bluetooth SIG members with helpful information and address frequently asked questions. Governing documents, membership agreements, policies, and other Bluetooth SIG rules and guidelines can be found here.)