-
Notifications
You must be signed in to change notification settings - Fork 64
Merge 1.0 into 2.0 #134
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
Merge 1.0 into 2.0 #134
Conversation
…entation to test with docker
…entation to test with docker
API-599: replace integration tests by end-to-end tests
CHANGELOG-1.0.md
Outdated
|
|
||
| ## Bug Fixes | ||
|
|
||
| - API-599: fix const not supported by PHP 5.6 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we first tag the 1.0.2 before merging 1.0 into 2.0 ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can merge before tag - it's not important no ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes you're right ^^
CHANGELOG-1.0.md
Outdated
|
|
||
| - API-599: fix const not supported by PHP 5.6 | ||
|
|
||
| # 1.0.1 (2018-04-05) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the 2.0 I did a single CHANGELOG. I think it's not necessary to do as the PIM and do a changelog for each version.
Having a common changelog between versions
No description provided.