Skip to content

Commit baad750

Browse files
committed
Add version table and update instructions.
1 parent 4317cc7 commit baad750

File tree

1 file changed

+29
-1
lines changed

1 file changed

+29
-1
lines changed

docs/versioning.md

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,6 @@ X.Y.Z
3030
| | +-- Backward Compatible changes (Patch release - bug fixes, small additions)
3131
| +---- Backward Compatible changes (Minor release - small new features, bug fixes)
3232
+------ Backward Incompatible changes (Major release - new features and/or major changes)
33-
3433
```
3534

3635
For example:
@@ -56,3 +55,32 @@ It MAY include patch level changes. Patch version MUST be reset to 0 when minor
5655
Major version **X** MUST be incremented for a release that introduces backward incompatible changes.
5756
A major release can also include minor and patch level changes.
5857
You must reset the patch and minor version to 0 when you change the major version.
58+
59+
## MFTF version table
60+
61+
This table lists the version of the MFTF that was released with a particular version of Magento.
62+
63+
|||
64+
|---|---|
65+
| Magento | MFTF |
66+
| 2.3.1 | 2.3.13 |
67+
| 2.3.0 | 2.3.9 |
68+
| 2.2.8 | 2.3.13 |
69+
| 2.2.7 | 2.3.8 |
70+
71+
## Updating MFTF
72+
73+
The MFTF and the Magento product have differing release cycles, with the MFTF releasing more frequently. To get the latest version of the MFTF, update the version number in `composer.json` and update the package.
74+
75+
1. Open `composer.json` at the <Magento root>.
76+
1. Find the MFTF listing:
77+
78+
```json
79+
"require-dev": {
80+
"friendsofphp/php-cs-fixer": "~2.13.0",
81+
"lusitanian/oauth": "~0.8.10",
82+
"magento/magento2-functional-testing-framework": "2.3.13",
83+
```
84+
85+
1. Update the version number and save.
86+
1. Run the `composer update` command.

0 commit comments

Comments
 (0)