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

Allow Symfony 2.8 #1

Merged
merged 5 commits into from
Jun 1, 2016
Merged

Allow Symfony 2.8 #1

merged 5 commits into from
Jun 1, 2016

Conversation

soullivaneuh
Copy link
Collaborator

@soullivaneuh soullivaneuh commented Jun 1, 2016

Symfony 2.8 IS the same as 3.0, but with the deprecated old feature.

This was done to provide an easy upgrading way between 2.x and 3.x.

Lot of people are still on 2.x version of Symfony.

Nothing has to be changed on the project codebase.

Plus, this is a LTS version. It's important to keep support on it.

Ref: http://symfony.com/blog/transition-from-symfony-2-7-to-3-0-symfony-2-8-on-its-way

Note I also removed the composer.lock file and replaced composer install by composer update.

As a library, dependencies tests should not be locked at all.

Travis was update to test multiple Symfony versions so you will have the proof that your bundle is compatible. 👍

@soullivaneuh soullivaneuh force-pushed the symfony-2.8 branch 4 times, most recently from 1485439 to 0dddc14 Compare June 1, 2016 11:19
@soullivaneuh
Copy link
Collaborator Author

soullivaneuh commented Jun 1, 2016

https://travis-ci.org/Algatux/influxdb-bundle/jobs/134418403#L171

Seems some of your dependencies are not compatible with Symfony 3.1.

Shall I remove this part?

Related issue: phpspec/prophecy#272
Related PR: phpspec/prophecy#275

@Algatux
Copy link
Owner

Algatux commented Jun 1, 2016

Hi thanks a lot for your pr. I will take a look as soon as possible.

Yes please remove symfony 3.1 for now.

As a library, dependencies tests should not be locked at all.
Symfony 2.8 IS the same as 3.0, but with the deprecated old feature.

This was done to provide an easy upgrading way between 2.x and 3.x.

Lot of people are still on 2.x version of Symfony.

Nothing has to be changed on the project codebase.

Plus, this is a LTS version. It's important to keep support on it.

Ref: http://symfony.com/blog/transition-from-symfony-2-7-to-3-0-symfony-2-8-on-its-way
The goal is to test the library against multiple versions of Symfony and with lowest dependencies.
@soullivaneuh
Copy link
Collaborator Author

@Algatux done! 👍

@Algatux Algatux merged commit a03702d into Algatux:master Jun 1, 2016
@soullivaneuh soullivaneuh deleted the symfony-2.8 branch June 1, 2016 13:16
@soullivaneuh
Copy link
Collaborator Author

Thanks you for the merge! 👍

Could you please tag a new release for that?

@soullivaneuh
Copy link
Collaborator Author

@Algatux I saw you did a merge by Squash. This is your choice, but I advice you to not do this if the PR contains multiple commits. In this case, each commit was about a specific subject. 😉

cc @greg0ire

@greg0ire
Copy link

greg0ire commented Jun 2, 2016

Those beautiful, verified commits… squashed…
so sad

@Algatux
Copy link
Owner

Algatux commented Jun 2, 2016

@soullivaneuh @greg0ire sorry for the squash guys! I was verry excited for the PR 😇

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.

None yet

3 participants