Skip to content

MQE-2203: Create CHANGELOG.MD entry for 3.0.0 #748

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 1 commit into from
Jun 26, 2020
Merged

MQE-2203: Create CHANGELOG.MD entry for 3.0.0 #748

merged 1 commit into from
Jun 26, 2020

Conversation

soumyau
Copy link
Contributor

@soumyau soumyau commented Jun 26, 2020

consolidated change log for 3.0.0

Description

Fixed Issues (if relevant)

  1. magento/magento2-functional-testing-framework#<issue_number>: Issue title
  2. ...

Contribution checklist

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/verification tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)
  • Changes to Framework doesn't have backward incompatible changes for tests or have related Pull Request with fixes to tests

consolidated change log for 3.0.0
@soumyau soumyau requested review from dobooth, okolesnyk and jilu1 June 26, 2020 17:14
@dobooth dobooth added the DOC label Jun 26, 2020
@coveralls
Copy link

Coverage Status

Coverage remained the same at 56.031% when pulling db284aa on MQE-2203 into c0255ee on develop.

@jilu1
Copy link
Contributor

jilu1 commented Jun 26, 2020

@soumyau
There are a lot of moving contents in this PR. It's not easy to tell if everything is accounted for. Spot check a few and they look good.

@okolesnyk
Since you requested this, do you like the idea to have to 3.0.0 as top level heading and keep sub heading like RC1, RC2, etc without changing the major contents?

@soumyau
Copy link
Contributor Author

soumyau commented Jun 26, 2020

@soumyau
There are a lot of moving contents in this PR. It's not easy to tell if everything is accounted for. Spot check a few and they look good.

@okolesnyk
Since you requested this, do you like the idea to have to 3.0.0 as top level heading and keep sub heading like RC1, RC2, etc without changing the major contents?

@jilu content is intact, sequence may have changed.

@soumyau soumyau merged commit f630b5d into develop Jun 26, 2020
jilu1 pushed a commit that referenced this pull request Jul 8, 2020
@tomreece tomreece deleted the MQE-2203 branch July 27, 2020 14:11
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.

5 participants