Release Policy

Introduction

• DDI-CDI is a new product, and we can expect issues and bugs to be reported as implementation takes place

• In the past, DDI has employed a mechanism for doing “beta” releases to test bug fixes before officially including them in the standard

• Other specifications have code repositories where a change request is accompanied by a branch of the code for the standard

• Could DDI-CDI adopt these mechanisms to help support implementation?

Planned Deliverables

• Recommended process for “beta” releases (etc.)

To be covered later in week – 2 sessions?