Skip to content
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

Update the name of the branch for new BC features #5421

Merged
merged 1 commit into from
Jun 28, 2015

Conversation

Restless-ET
Copy link
Contributor

Q A
Doc fix? yes
New docs? no
Applies to 2.3+
Fixed tickets -

Updated section Choose the right Branch to refer branch 2.8 as the one for new BC features.

PS- Will this be merged into other the branches or should I create a PR for the other ones too.

@xabbuh
Copy link
Member

xabbuh commented Jun 22, 2015

Great catch @Restless-ET 👍

And by the way, after this has been merged into the 2.3 branch, it will be merged up to the other branches. So there's no need to create PRs for the other branches.

@Restless-ET
Copy link
Contributor Author

😄 I thought something like that would take place. Thanks for the confirmation @xabbuh.

@xabbuh
Copy link
Member

xabbuh commented Jun 28, 2015

Good catch, thanks @Restless-ET.

@xabbuh xabbuh merged commit ac0a90a into symfony:2.3 Jun 28, 2015
xabbuh added a commit that referenced this pull request Jun 28, 2015
…ss-ET)

This PR was merged into the 2.3 branch.

Discussion
----------

Update the name of the branch for new BC features

| Q             | A
| ------------- | ---
| Doc fix?      | yes
| New docs?     | no
| Applies to    | 2.3+
| Fixed tickets | -

Updated section ```Choose the right Branch``` to refer branch ```2.8``` as the one for new BC features.

PS- Will this be merged into other the branches or should I create a PR for the other ones too.

Commits
-------

ac0a90a Update branch for new BC features
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants