-
Notifications
You must be signed in to change notification settings - Fork 379
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 2.0 branch into master #1201
Conversation
[enqueue] Improve doc.
Move to trusty for travis except for php 5.3
return filter function String
Typo at log message
…m-allowed-failures Remove Symfony 3.3 from allowed failures
Add chain loader implementation
Add chain loader documentation
…d-of-version-numbers Use simplified Symfony version comparison operation and CS fixes
[Composer] Allow imagine-library version 0.7.0
- Allow construction of Locator without data roots for BC - Mark FilesystemLocator::setOptions deprecated
Modify some PHP Annotations
Added support for centerright and centerleft position
Update png-quant.rst
Fix nested level of bucket parameter
fix annotation
[Filter] Add "fixed-size" filter implementation
Replace app/console with bin/console
* Updated Dynamic filters * Added info about autowiring. This is the most important part - took me some time to figure it out. * "Moved" sample code from a controller to a service * Deleted info about outdated Symfony 2.4
Upgrade 2.0 from 1.0
i am confused by the branches in this repository. master currently only has the alias that 1.0-dev is version 1, but has no alias for what the master branch should see. if master is 2.x, we should not have a 2.0 branch. if master is 1.x we should not have had the 1.0 branch and should rather merge 1.0 to master than merge 2.0 to master. note that there is no release of version 2 yet, so master can't mean 3.x. @lsmith77 or @michellesanver can one of you help us out here and clarify this? |
@maximgubar might remember the details .. but afaik 2.0 was used to prepare the 2.0 release .. after the 2.0 release, master became the source for 2.0 releases .. but I am not 100% sure |
oh, i overlooked the 2.0.0 and 2.1.0 releases because older tags use the and imho there should be a branch alias for |
looking at 2.0...master there seem to be cs cleanups and one big new feature, the configuration model classes. i don't think they are a BC break, so imho we can merge this and then remove the 2.0 branch for clarity. wdyt @michellesanver ? |
Sounds like a perfect plan! :) |
This is like #1199, merging 2.0 branch into master so lost commits are recovered in
master
as well