Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
MAGEDOC-3691: Release page update (#4246)
* MAGEDOC-3691: Created new page for policy and changed references to release candidate and stable * MAGEDOC-3691: Updated release policy per PdM feedback * MAGEDOC-3691: Updated links * MAGEDOC-3691: Replaced plain text product name with var * MAGEDOC-3691: More revisions per PdM feedback * MAGEDOC-3691: More revisions per PdM feedback
- Loading branch information
1 parent
218902f
commit 4fbdfa9
Showing
10 changed files
with
79 additions
and
53 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -143,6 +143,7 @@ relative_links: | |
| - extensions | ||
| - guides | ||
| - redoc | ||
| - release | ||
| - tmp | ||
| - 404.md | ||
| - availability.md | ||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| label: Release Information | ||
| pages: | ||
|
|
||
| - label: Upcoming releases | ||
| url: /release/ | ||
| versionless: true | ||
|
|
||
| - label: Release policy | ||
| url: /release/policy | ||
| versionless: true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,50 +1,29 @@ | ||
| --- | ||
| layout: full-width | ||
| title: Magento product release information | ||
| title: Upcoming releases | ||
| group: release | ||
| --- | ||
|
|
||
| Magento releases security and functional patches for each supported release line of {{site.data.var.ee}} every quarter. | ||
| Magento continually strives to find the right balance between making product upgrades simple and predictable and delivering improvements and new features to early adopters faster. Over the last year, we have refined how we deliver software to support this balance. For additional information, refer to our [release policy]({{site.baseurl}}/release/policy/). | ||
|
|
||
| The following guidelines apply to patch releases: | ||
| ## Availability | ||
|
|
||
| - All supported versions receive security fixes. | ||
| - Newer versions receive full functional fixes and any enhancements. Fixes for high-severity functional issues are back-ported to older supported versions, but fixes for lower-severity issues are not necessarily back-ported. | ||
| - Changes that could break extensions or code compatibility are avoided. For example, code written for 2.2.0 should still work on 2.2.7. | ||
| - On an exceptional basis, breaking changes or additional patches or hotfixes may be released to address security issues. On the module level, these are mostly PATCH level changes, sometimes MINOR level changes. | ||
| - Patches may include new features as long as they are not expected to break other code. The new feature can be included in the core code or as an extension, such as Page Builder. | ||
|
|
||
| Magento releases a large (minor version change – 2.2.0 -> 2.3.0) update about once a year. | ||
|
|
||
| The following guidelines apply to minor releases: | ||
|
|
||
| - Breaking changes are possible; code written for 2.2.x may no longer work with 2.3.x. For example, minor releases can introduce support for major system requirements and dependencies, such as PHP. | ||
| - Module versions can vary. For example, some module changes are introduced in a new patch whereas others are introduced in a major release. | ||
| - Minor release can include new features that may require additional work from partners during upgrade to ensure compatibility. | ||
|
|
||
| {:.bs-callout .bs-callout-info} | ||
| See [Magento Software Lifecycle Policy] and [Versioning]. | ||
|
|
||
| ## Product availability | ||
| The following table describes the status of Magento software availability and where to get it, particularly for software that is available outside the conventional {{site.data.var.ee}} Composer package. | ||
|
|
||
| | Product | Availability | How to get it | | ||
| |-------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------| | ||
| | **{{site.data.var.ee}} 2.3.1 GA** | Available now | [Composer](https://devdocs.magento.com/guides/v2.3/install-gde/composer.html) | | ||
| | **{{site.data.var.ee}} 2.3.0 GA** | Available now | [Composer](https://devdocs.magento.com/guides/v2.3/install-gde/composer.html) | | ||
| | **{{site.data.var.ee}} 2.3.1 GA** | Available now | [Composer](https://devdocs.magento.com/guides/v2.3/install-gde/composer.html) | | ||
| | **{{site.data.var.ee}} 2.3.0 GA** | Available now | [Composer](https://devdocs.magento.com/guides/v2.3/install-gde/composer.html) | | ||
| | **{{site.data.var.ece}} Tools (aka ECE-Tools)** | Available now | [Composer](https://devdocs.magento.com/guides/v2.3/cloud/project/ece-tools-update.html) | | ||
| | **PWA Studio** | Available now (including support for {{site.data.var.ece}}) | [Documentation](https://magento-research.github.io/pwa-studio/) and [GitHub](https://github.com/magento-research/pwa-studio) | | ||
| | **Magento Shipping** | Available now | Merchants on Magento 2.2.2+ can use the [onboarding process](https://account.magento.com/shipping/onboarding/start) | | ||
| | **Page Builder** | Available now | Bundled with Magento Commerce 2.3.x | | ||
| | **Amazon Sales Channel** | Early access closed<br><br>Regional availability expected in first half of 2019 (US, Canada, Mexico)<br><br>EMEA and APAC availability expected in second half of 2019 | Magento Marketplace | | ||
| | **Google Shopping Ads Channel** | Early access May 2019<br><br>General availability expected in first half of 2019 | Magento Marketplace | | ||
| | **Google Shopping Ads Channel** | Early access May 2019<br><br>General availability expected in first half of 2019 | Magento Marketplace | | ||
|
|
||
| ## Compatibility | ||
|
|
||
| ## Extension stability | ||
| Magento modules that have been built to be decoupled from the {{site.data.var.ee}} core release process; this allows us to release iterations of these modules faster to merchants who are willing to accept a little risk in exchange for earlier access to new features. | ||
|
|
||
| The following table shows the release status of Magento extension versions relative to the 2.3.x release line of {{site.data.var.ee}}. | ||
|
|
||
| {% include compatibility.html data=site.data.compatibility %} | ||
|
|
||
| <!-- Link definitions --> | ||
|
|
||
| [Versioning]: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/versioning/ | ||
| [Magento Software Lifecycle Policy]: https://magento.com/sites/default/files/magento-software-lifecycle-policy.pdf |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,36 @@ | ||
| --- | ||
| title: Release policy | ||
| group: release | ||
| --- | ||
|
|
||
| {{site.data.var.ee}} uses [semantic versioning](https://semver.org/). For example: | ||
|
|
||
| - **MAJOR**—2 | ||
| - **MINOR**—2.3 | ||
| - **PATCH**—2.3.1 | ||
|
|
||
| ## MINOR release | ||
|
|
||
| Magento releases a large, minor version of {{site.data.var.ee}} about once a year. | ||
|
|
||
| The following guidelines apply to minor releases: | ||
|
|
||
| - Breaking changes are possible; code written for 2.2.x may no longer work with 2.3.x. For example, minor releases can introduce support for major system requirements and dependencies, such as PHP. | ||
| - Module versions can vary. For example, some module changes are introduced in a new patch whereas others are introduced in a major release. | ||
| - Minor releases can include new features that may require additional work from partners during upgrade to ensure compatibility. | ||
| - Minor releases can include fixes for security and compliance issues. | ||
|
|
||
| ## PATCH release | ||
|
|
||
| Patch releases are primarily focused on delivering security and quality enhancements on a regular basis to help you keep your sites performing at their peak. Magento releases security and functional patches for each supported release line of {{site.data.var.ee}} every quarter. | ||
|
|
||
| The following guidelines apply to patch releases: | ||
|
|
||
| - All supported versions receive security fixes. | ||
| - Newer versions receive full functional fixes and enhancements. | ||
| - Changes that could break extensions or code compatibility are avoided. For example, code written for 2.2.0 should still work on 2.2.7. | ||
| - On an exceptional basis, breaking changes or additional patches or hotfixes may be released to address security or compliance issues. On the module level, these are mostly PATCH-level changes; sometimes MINOR-level changes. | ||
| - Patches may include new features as long as they are not expected to break other code. The new feature can be included in the core code or as an extension, such as Page Builder. | ||
|
|
||
| {:.bs-callout .bs-callout-info} | ||
| See [Magento Software Lifecycle Policy](https://magento.com/sites/default/files/magento-software-lifecycle-policy.pdf) and [Versioning](https://devdocs.magento.com/guides/v2.3/extension-dev-guide/versioning/). |