Add blogpost about v0 recipe changes (#190)

Co-authored-by: jaimergp <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Bianca Henderson <[email protected]>
Co-authored-by: Katherine Kinnaman <[email protected]>

blog/2024-11-15-v0-format-modifications.mdx

@@ -0,0 +1,62 @@
+---
+title: "Navigating Change in Conda-Build Recipe Formats: Balancing Legacy and Innovation"
+slug: "2024-11-15-v0-format-modifications"
+authors: [kenodegard]
+tags: [announcement, conda, conda-build, recipe, cep-13, cep-14]
+description: >
+  The recent approval of the new recipe format (`recipe.yaml`, v1) does not mean the end of the
+  old format (`meta.yaml`, v0). The conda community must balance innovation with support for
+  legacy systems.
+image: img/blog/2024-11-15-v0-format-modifications/banner.png
+---
+
+[cep-13]: https://github.com/conda/ceps/blob/main/cep-13.md
+[cep-14]: https://github.com/conda/ceps/blob/main/cep-14.md
+[rattler-build]: https://prefix-dev.github.io/rattler-build/latest/
+[ceps]: https://github.com/conda/ceps
+[rattler-recipe]: https://prefix-dev.github.io/rattler-build/latest/reference/recipe_file/
+[rattler-migration]: https://prefix-dev.github.io/rattler-build/latest/converting_from_conda_build/
+[crm]: https://conda-incubator.github.io/conda-recipe-manager/index.html
+
+The recent approval of a new recipe format (v1) by the Conda Steering Council
+via [CEP-13][cep-13] and [CEP-14][cep-14] marks an important milestone in the
+evolution of package management in the conda ecosystem. While the community
+embraces the potential improvements that come with the new format, we
+acknowledge that the v1 recipe format is still undergoing development
+in [rattler-build][rattler-build]. Consequently, the v0 recipe
+format remains widely in use, emphasizing the need to balance innovation with support
+for legacy systems.
+
+<!-- truncate -->
+
+While the focus is on innovating with the v1 format, the transition and adoption
+will take time. In the meantime, we still need to remain responsive to the challenges
+and requirements of those who continue to rely on the v0 format for their packaging
+needs. Updates to the v0 format should be driven by the needs of the user
+community, guided by user feedback, and aimed at addressing pain points.
+
+To initiate changes to the v0 conda-build recipe format, the following workflow
+is followed:
+
+1. **Conda Enhancement Proposal**: Any proposed modifications to the v0 format should
+   also be proposed in the v1 format. The rationale being, if it's necessary for v0
+   it should also be necessary for v1. All proposals go through the CEP process;
+   see [CEPs][ceps].
+2. **Review & Approval**: The proposed modification will undergo the CEP review and
+   approval process and results in a v1 recipe format `schema_version` bump.
+3. **Implementation**: Once approved, the changes can be implemented in the v0
+   format, ensuring alignment with the corresponding features in the v1 format.
+
+As the community navigates the transition from v0 to v1, we aim to offer clear
+communication and guidance. Developers and maintainers need to be equipped with the
+resources and support necessary to understand the implications of the new format
+and make informed decisions about when and how to migrate (see
+[rattler-build's recipe docs][rattler-recipe],
+[rattler-build's migration docs][rattler-migration], and [conda-recipe-manager docs][crm]).
+
+The approval of the v1 format represents an exciting step forward for the conda
+ecosystem. However, it's essential to recognize that change takes time, and the
+transition to the new format will be gradual. In the interim, the v0 format
+remains a critical component of the conda ecosystem and requires ongoing
+support and updates. As always the goal is to offer a smooth transition to the new
+standards while continuing to support the existing infrastructure and user base.

blog/news.json

@@ -1,4 +1,22 @@
 [
+  {
+    "title": "Navigating Change in Conda-Build Recipe Formats: Balancing Legacy and Innovation",
+    "slug": "2024-11-15-v0-format-modifications",
+    "authors": [
+      "kenodegard"
+    ],
+    "tags": [
+      "announcement",
+      "conda",
+      "conda-build",
+      "recipe",
+      "cep-13",
+      "cep-14"
+    ],
+    "description": "The recent approval of the new recipe format (`recipe.yaml`, v1) does not mean the end of the old format (`meta.yaml`, v0). The conda community must balance innovation with support for legacy systems.\n",
+    "image": "img/blog/2024-11-15-v0-format-modifications/banner.png",
+    "date": "2024-11-15T00:00:00"
+  },
   {
     "title": "October 2024 Releases",
     "slug": "2024-10-21-october-releases",
@@ -57,21 +75,5 @@
     "description": "The first \"chatting with the conda community\" is talking about the origins of conda-forge - with Filipe Fernandes.",
     "image": "img/blog/2024-09-chatting-with-conda-community/banner.png",
     "date": "2024-09-12T00:00:00"
-  },
-  {
-    "title": "Conda Ecosystem Explained",
-    "slug": "2024-08-14-conda-ecosystem-explained",
-    "authors": [
-      "dashagurova",
-      "jezdez"
-    ],
-    "tags": [
-      "conda",
-      "community",
-      "governance"
-    ],
-    "description": "Get to know the conda ecosystem\u2014a vibrant community supporting an open-source, language-agnostic, and multi-platform package management system. Discover conda CLI tools for managing packages and environments, and explore key repositories like conda-forge, bioconda and defaults. You will learn how to get started with conda tools, the important things to keep in mind, and how multistakeholder governance ensures the ecosystem remains reliable and accessible to all.\n",
-    "image": "img/blog/2024-08-14-conda-ecosystem-explained/banner.png",
-    "date": "2024-08-14T00:00:00"
   }
 ]