diff --git a/_images/q2-dev-cycle-diagram.png b/_images/q2-dev-cycle-diagram.png index c018567..6501552 100644 Binary files a/_images/q2-dev-cycle-diagram.png and b/_images/q2-dev-cycle-diagram.png differ diff --git a/_sources/framework/references/dev-cycle-structure.md b/_sources/framework/references/dev-cycle-structure.md index 5af7b0a..db7c0a6 100644 --- a/_sources/framework/references/dev-cycle-structure.md +++ b/_sources/framework/references/dev-cycle-structure.md @@ -7,7 +7,7 @@ If you have any questions on this process, please don't hesitate to reach out on ## QIIME 2 Release Cycle Structure As of 2024.10, QIIME 2 Distributions are released bi-anually, on the first Wednesday of April and October. -This schedule provides us with ample development time between releases, and provides our developer community with at least a three month notice for any external dependency changes (i.e. bumping Python, removing a deprecated package, etc). +This schedule provides us with ample development time between releases, and provides our developer community with at least a three month notice for any interface/API changes and any external dependency changes (i.e. bumping Python, removing a deprecated package, etc). The following diagram outlines relevant timepoints between each release, with terms defined below. diff --git a/framework/references/dev-cycle-structure.html b/framework/references/dev-cycle-structure.html index 26091ab..088b28d 100644 --- a/framework/references/dev-cycle-structure.html +++ b/framework/references/dev-cycle-structure.html @@ -448,7 +448,7 @@
As of 2024.10, QIIME 2 Distributions are released bi-anually, on the first Wednesday of April and October. -This schedule provides us with ample development time between releases, and provides our developer community with at least a three month notice for any external dependency changes (i.e. bumping Python, removing a deprecated package, etc).
+This schedule provides us with ample development time between releases, and provides our developer community with at least a three month notice for any interface/API changes and any external dependency changes (i.e. bumping Python, removing a deprecated package, etc).The following diagram outlines relevant timepoints between each release, with terms defined below.