Skip to content

Add version table and update instructions. #350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
May 22, 2019

Conversation

dobooth
Copy link
Contributor

@dobooth dobooth commented May 9, 2019

Description

Adds a magento2 -> MFTF version table.
Adds instructions for updating MFTF.

@dobooth dobooth requested a review from tomreece May 9, 2019 17:33
@dobooth dobooth self-assigned this May 9, 2019
@coveralls
Copy link

coveralls commented May 9, 2019

Coverage Status

Coverage remained the same at 55.958% when pulling 40d16e6 on magento-devdocs:db_version_table into 291bad3 on magento:develop.

@dobooth dobooth added the DOC label May 9, 2019
@dobooth dobooth requested a review from dshevtsov May 10, 2019 14:48
| 2.2.8 | 2.3.13 |
| 2.2.7 | 2.3.8 |

## Updating MFTF
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a topic about MFTF update: https://devdocs.magento.com/mftf/docs/update.html
Shouldn't it go there?
By the way, the topic uses composer update to update dependencies. (This should be reviewed I believe because this command updates all Magento dependencies, not only MFTF).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed.

@@ -56,3 +55,15 @@ It MAY include patch level changes. Patch version MUST be reset to 0 when minor
Major version **X** MUST be incremented for a release that introduces backward incompatible changes.
A major release can also include minor and patch level changes.
You must reset the patch and minor version to 0 when you change the major version.

## MFTF version table
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The section title doesn't describe its substance. The topic itself is about MFTF versioning and we see that it contains a table. The heading should give an idea of what is in that table.
Consider renaming to something like:
Relation to Magento releases

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

Copy link
Contributor

@dshevtsov dshevtsov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added minor suggestion

@@ -56,3 +55,14 @@ It MAY include patch level changes. Patch version MUST be reset to 0 when minor
Major version **X** MUST be incremented for a release that introduces backward incompatible changes.
A major release can also include minor and patch level changes.
You must reset the patch and minor version to 0 when you change the major version.

## Magento 2 compatibility
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Magento 2 compatibility
## Magento 2 compatibility

@tomreece tomreece merged commit a779d9b into magento:develop May 22, 2019
@dobooth dobooth deleted the db_version_table branch August 9, 2019 14:48
magento-devops-reposync-svc pushed a commit that referenced this pull request Nov 16, 2023
Merging master back to develop .
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants