You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: src/guides/v2.3/extension-dev-guide/versioning/codebase-changes.md
+16-10Lines changed: 16 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -3,19 +3,18 @@ group: php-developer-guide
3
3
title: Codebase changes
4
4
---
5
5
6
-
Every Magento version release includes a change in the codebase.
7
-
The scope of the change determines whether the MAJOR, MINOR, or PATCH number increases in the version.
6
+
Every release includes a change in the codebase. The scope of the change determines whether the MAJOR, MINOR, or PATCH number increases in the version.
8
7
9
8
## Public vs private code changes
10
9
11
-
A Magento module's codebase consists of public and private code.
10
+
A module's codebase consists of public and private code.
12
11
Public code includes Public [API](https://glossary.magento.com/api)(indicated by the `@api` docblock tag) and Public Customization Points.
13
12
All other code is considered private.
14
13
15
14
Changes in public code always trigger MINOR or MAJOR version increases.
16
15
17
16
In most cases, modifications to private code will trigger PATCH version increases.
18
-
On rare occasions, if the Magento development team made significant modifications to private code, they will increase the MINOR or MAJOR version.
17
+
On rare occasions, if the Adobe development team made significant modifications to private code, they will increase the MINOR or MAJOR version.
19
18
20
19
Third-party modules should not use private code.
21
20
If this is unavoidable, you must depend on the PATCH version of the core modules used.
@@ -30,13 +29,13 @@ Modifications that break Customization Points will trigger an increase in a modu
30
29
31
30
An interface represents either an API or a Customization Point.
32
31
33
-
This policy allows third-party module developers to declare more granular dependencies depending on their module's interaction with Magento modules.
32
+
This policy allows third-party module developers to declare more granular dependencies depending on their module's interaction with core modules.
34
33
35
34
## Deprecation
36
35
37
-
Marking public code with `@deprecated` indicates that Magento plans to remove that code in a future MINOR release.
36
+
Marking public code with `@deprecated` indicates that Adobe plans to remove that code in a future MINOR release or potentially after a year if no MINOR version is released.
38
37
39
-
When Magento deprecates the API or a customization point in favor of a new implementation, the `@see` annotation points to the new implementation.
38
+
When Adobe deprecates the API or a customization point in favor of a new implementation, the `@see` annotation points to the new implementation.
40
39
41
40
**Deprecated Code Example:**
42
41
@@ -55,7 +54,7 @@ public function save()
55
54
## Version increase scenarios
56
55
57
56
This table lists code change scenarios and which version number it affects.
58
-
Use this table to understand what changes Magento can make and which version number gets increased for that change.
57
+
Use this table to understand what changes Adobe can make and which version number gets increased for that change.
59
58
Any change not listed below is considered a PATCH level change.
60
59
61
60
| API/Customization Point | Code Change| Version Change |
@@ -162,7 +161,7 @@ Any change not listed below is considered a PATCH level change.
162
161
163
162
### PHP Classes Intended for Extension
164
163
165
-
Though inheritance is discouraged in Magento, the following classes are still acceptable for extension at the moment:
164
+
Though inheritance is discouraged, the following classes are still acceptable for extensions at the moment:
Copy file name to clipboardExpand all lines: src/guides/v2.3/extension-dev-guide/versioning/index.md
+16-14Lines changed: 16 additions & 14 deletions
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
2
group: php-developer-guide
3
-
title: Magento versioning schema
3
+
title: Versioning schema
4
4
redirect_from:
5
5
- /guides/v2.3/architecture/versioning.html
6
6
---
7
7
8
-
Magento software and Magento module releases have their own unique version number.
8
+
{{site.data.var.ee}} and {{site.data.var.ce}} application and module releases have their own unique version number.
9
9
10
-
## Software version format
10
+
## Application version format
11
11
12
-
A change in the version for the Magento software indicates a patch or feature release.
12
+
A change in the version for the application indicates a patch or feature release.
13
13
This version change does not reflect the nature of the changes in the code base.
14
14
15
15
## Module version format
@@ -24,6 +24,9 @@ The format follows [Semantic Versioning][semantic-versioning] rules for any `@ap
24
24
* The MINOR version increments when backward-compatible functionality has been added or if the module's customization points have changed.
25
25
* The PATCH version increments when backward-compatible bug fixes occur.
26
26
27
+
{:.bs-callout-info}
28
+
On an exceptional basis, breaking changes or additional patches or hotfixes may be released on a PATCH version to address security or compliance issues and high-impact quality issues.
29
+
27
30
### Pre-release versions
28
31
29
32
For pre-release versions, the format is:
@@ -33,15 +36,15 @@ For pre-release versions, the format is:
33
36
|`alpha`, `beta` or `rc`| Stability indicators, as described in the [`version_compare()`][php-version-compare]{:target="_blank"} specification|
34
37
|`n`| An increment number to distinguish releases of the non-stable versions |
35
38
36
-
Magento's module versioning policy complies with the following specifications:
39
+
Adobe's module versioning policy complies with the following specifications:
The software version can be found in the source code of any [Magento component](https://glossary.magento.com/magento-component) or bundle, inside the `composer.json` file.
47
+
The application version can be found in the source code of any [component](https://glossary.magento.com/magento-component) or bundle inside the `composer.json` file.
45
48
46
49
It can be declared as the version of the component:
47
50
@@ -59,16 +62,15 @@ Or it can be used to declare a dependency on a particular version of a component
59
62
}
60
63
```
61
64
62
-
{:.bs-callout-info}
63
-
If Magento is installed from GitHub without using Composer, the `version` is not included. Admin displays the version as `Magento ver. dev-<GitHub-branch-name>`. In addition, Magento modules inside the `require` declaration list a version of `*`. For example, `"magento/framework": "*"`
64
-
65
-
## Related Topics
66
-
67
-
[Module version dependencies][version-dependencies] - Information about how your module can depend on the version of other modules.
65
+
{:.bs-callout-info}
66
+
If you installed the application from GitHub without using Composer, the `version` is not included. The Admin displays the version as `Magento ver. dev-<GitHub-branch-name>`. In addition, modules inside the `require` declaration list a version of `*`. For example, `"magento/framework": "*"`.
68
67
69
-
[Codebase changes][codebase-changes] - Information on how changes in a Magento module's codebase affect versions.
68
+
{:.ref-header}
69
+
Related Topics
70
70
71
-
[Backward compatible development]({{ site.baseurl }}/contributor-guide/backward-compatible-development/index.html) - Information about MAJOR and MINOR changes and how they impact extension developers.
71
+
*[Module version dependencies][version-dependencies] - Information about how your module can depend on the version of other modules.
72
+
*[Codebase changes][codebase-changes] - Information on how changes in a module's codebase affect versions.
73
+
*[Backward compatible development]({{ site.baseurl }}/contributor-guide/backward-compatible-development/index.html) - Information about MAJOR and MINOR changes and how they impact extension developers.
Copy file name to clipboardExpand all lines: src/release/index.md
+22-15Lines changed: 22 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -3,29 +3,30 @@ title: Upcoming releases
3
3
group: release
4
4
---
5
5
6
-
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/).
6
+
Adobe 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/).
7
7
8
8
## Release schedule
9
9
10
-
Magento releases security and functional patches for each supported release line of {{site.data.var.ee}} every quarter.
10
+
Adobe releases security and functional patches for each supported release line of {{site.data.var.ee}} and {{site.data.var.ce}}.
11
11
12
-
The following table provides the dates for scheduled releases in 2021 (dates are subject to change):
12
+
The following table provides the dates for scheduled releases (dates are subject to change):
| October 2021<br>Security patch release | 2.4.3-p1<br>2.3.7-p2 |\-\-| September 28, 2021 | October 12, 2021 |
17
+
| January 2022<br>Feature release |\-\-|\-\-|\-\-| January 18, 2022 |
18
+
| March 2022<br>Feature + patch release | 2.4.4<br>2.4.3-p2<br>2.3.7-p3<sup>1</sup> | October 2021 and ongoing | February 22, 2022 | March 8, 2022 |
19
+
| April 2022<br>Feature release |\-\-|\-\-|\-\-| April 26, 2022 |
20
+
| June 2022<br>Feature release |\-\-|\-\-|\-\-| June 21, 2022 |
21
+
| August 2022<br>Feature + patch release | 2.4.5<br>2.4.4-p1 |\-\-| July 26, 2022 | August 9, 2022 |
22
+
| October 2022<br>Feature + security patch release | 2.4.5-p1<sup>2</sup> |\-\-| September 27, 2022 | October 11, 2022 |
20
23
21
-
_<sup>1</sup>If you take the 2021 Q2 2.3.x release line, you must [update to PHP 7.4](https://community.magento.com/t5/Magento-DevBlog/PHP-7-4-support-for-Magento-2-3-x-release-line/ba-p/458946) since PHP 7.3 reaches end-of-life in December 2021. There will not be a 2.4.3 release in 2021 Q2._
22
-
23
-
_<sup>2</sup>The 2021 Q3 release will return to normal with a security-only release for the 2.3.x release line using PHP 7.4._
24
-
25
-
_<sup>3</sup>There will not be a 2.4.4 release in 2021 Q4._
24
+
<sup>\-\- Indicates items that are not applicable to this release.</sup><br>
25
+
<sup>1 This is the last patch release for the 2.3.x release line. The 2.3.x release line reaches End of Life (EOL) in April 2022.</sup><br>
26
+
<sup>2 There is no full patch release in October 2022.</sup><br>
26
27
27
28
{:.bs-callout-info}
28
-
We have introduced a [new policy](https://magento.com/updated-lifecycle-policy-magento-releases) that applies to a previous, supported Magento release line.
29
+
We have introduced a [new policy](https://magento.com/sites/default/files/magento-software-lifecycle-policy.pdf) that applies to our supported release lines. To learn more about the new strategy behind our 2022 release calendar and lifecycle policy, visit our [blog](https://magento.com/blog/magento-news/accelerating-innovation-through-simplified-release-strategy).
29
30
30
31
## Early access
31
32
@@ -34,3 +35,9 @@ Pre-release is General Availability code that is available to {{site.data.var.ee
34
35
Beta is non-General Availability code that is available to all partners. It allows for extra time to review code and affected components.
35
36
36
37
For information about our Beta program, go to our [GitHub wiki page](https://github.com/magento/magento2/wiki/Magento-Beta-Program).
38
+
39
+
## Release types
40
+
41
+
-**Patch releases**—Updates to the core {{site.data.var.ee}} and {{site.data.var.ce}} application that include security, compliance, performance, and high-priority quality fixes.
42
+
-**Security patch releases**—Security-only updates to the {{site.data.var.ee}} and {{site.data.var.ce}} application released to keep merchants secure and compliant.
43
+
-**Feature releases**—New features and feature updates that are delivered as independent services, separate from the patch releases. Examples include services like Product Recommendations and Live Search, independent modules like PWA Studio and Inventory Management (MSI), and updates to our cloud services and infrastructure.
For {{site.data.var.ece}} 2.3 and subsequent releases:
7
+
For {{site.data.var.ee}} 2.3 and subsequent releases:
7
8
8
-
-Magento will provide quality fixes for a minor release for a minimum of 12 months from the general availability announcement date of the next minor software release.
9
+
-{{site.data.var.ee}} will provide quality fixes for a minor release for a minimum of 12 months from the general availability announcement date of the next minor software release.
9
10
10
-
-Magento will provide security fixes for a minor release for a minimum of 18 months from the general availability announcement date of the next minor software release.
11
+
-{{site.data.var.ee}} will provide security fixes for a minor release for a minimum of 18 months from the general availability announcement date of the next minor software release.
11
12
12
-
-Magento will provide security fixes through patch releases for currently supported minor release versions only. Security fixes will not be backported to previous minor releases, nor to previous patch releases within supported minor releases.
13
+
-{{site.data.var.ee}} will provide security fixes through patch releases for currently supported minor release versions only. Security fixes will not be backported to previous minor releases, nor to previous patch releases within supported minor releases.
13
14
14
-
For example, while 2.3 and 2.4 are currently supported minor releases, security fixes will be released as 2.3.X and 2.4.Y, where X and Y represent the next incremental patch release cumulative of all prior patches. Patch releases will not be released for prior minor releases that have reached end of support (for example, 2.2.Z), or as patches to prior patch releases (for example, 2.3.1.X).
15
+
For example, while Adobe will provide security releases to its 2.3 release line until April 2022, customers must upgrade to the latest patch or security patch to access security fixes. When 2.3.7-p1 is released, customers must upgrade to 2.3.7-p1 to adopt the security fixes. The security fixes will not be backported to previous patch releases of the 2.3 release line (2.3.0-2.3.6-p1).
15
16
16
-
-Magento will provide quality fixes through patch release for the latest supported minor release version only. Quality fixes will be available as individual patches for all other currently supported minor release versions. Quality fixes will not be backported to other previous minor releases, nor to previous patch releases within supported minor releases.
17
+
-To better streamline our lifecycle policy, {{site.data.var.ee}} will provide quality fixes to its 2.4 release line until the end of support date of the PHP version upon which it is based. Refer to the table below for the End of Software Support dates for {{site.data.var.ee}} release lines:
17
18
18
-
For example, while 2.3 and 2.4 are currently supported minor releases, individual patches will be released as 2.3.X and release patches will be released as 2.4.Y, where X and Y represent the next incremental patch release cumulative of all prior patches. Neither patch releases nor individual patches will be released for prior minor releases that have reached end of support (e.g. 2.2.2).
19
+
| Release | Release Date | End of Software Support<sup>1</sup> | Dependent PHP Version |
0 commit comments