# Major releases procedure A major release consists of significant changes, that are not backwards compatible (i.e. breaking changes). A major release must be reviewed and signed off by at least 2 members of the ontology team. All partner platforms will be notified through their contact email. Platforms must respond confirming acceptance of the release before proceeding to public notification. A major release will then be publicly notified (a minimum of 10 days in advance of release) by broadcast on Slack & Github. After the appropriate notice period, the release will be marked as "Latest Release" --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.dfc-standard.org/dfc-standard-documentation/dfc-use-cases/contributing/general-decisions/updates-to-the-ontology/major-releases-procedure.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.