An update has been submitted to update EPEL 7's php-symfony package from version 2.5.12 to LTS version 2.7.7. The EPEL 7 php-symfony package will remain at LTS version 2.7.x.
* Full upstream changelogs: ** 2.6.x: https://github.com/symfony/symfony/blob/v2.7.7/CHANGELOG-2.6.md ** 2.7.x: https://github.com/symfony/symfony/blob/v2.7.7/CHANGELOG-2.7.md * Upgrade guides: ** Upgrade from 2.5 to 2.6: https://github.com/symfony/symfony/blob/v2.7.7/UPGRADE-2.6.md ** Upgrade from 2.6 to 2.7: https://github.com/symfony/symfony/blob/v2.7.7/UPGRADE-2.7.md
Bodhi update: https://bodhi.fedoraproject.org/updates/php-twig-1.23.1-2.el7%20php-symfony-...
On Tue, Dec 8, 2015 at 7:23 PM, Shawn Iwinski shawn.iwinski@gmail.com wrote:
An update has been submitted to update EPEL 7's php-symfony package from version 2.5.12 to LTS version 2.7.7. The EPEL 7 php-symfony package will remain at LTS version 2.7.x.
- Full upstream changelogs: ** 2.6.x:
https://github.com/symfony/symfony/blob/v2.7.7/CHANGELOG-2.6.md ** 2.7.x: https://github.com/symfony/symfony/blob/v2.7.7/CHANGELOG-2.7.md
- Upgrade guides: ** Upgrade from 2.5 to 2.6:
https://github.com/symfony/symfony/blob/v2.7.7/UPGRADE-2.6.md ** Upgrade from 2.6 to 2.7: https://github.com/symfony/symfony/blob/v2.7.7/UPGRADE-2.7.md
Bodhi update: https://bodhi.fedoraproject.org/updates/php-twig-1.23.1-2.el7%20php-symfony-...
According to the Symfony website, version 2.8 is the LTS version[1], so why 2.7?
[1]: http://symfony.com/roadmap%E2%80%8B
On 12/09/2015 06:17 AM, Neal Gompa wrote:
According to the Symfony website, version 2.8 is the LTS version[1], so why 2.7?
It seems 2.7 is also a LTS version.
Symfony 2.7 is a long term support version with 3 years support that was published in May 2015.
May 2018 End of support for bug fixes
Cheers, François
Correct... 2.7 is also a LTS version [1][2]. It was originally planned to be the last 2.x release as well as the last 2.x LTS version. See [2] for where 2.8 came from.
Not many of my packages use/require 2.8 though so my current plan is to stick with 2.7. We can discuss 2.8 if it is needed though.
[1] http://symfony.com/roadmap?version=2.7#checker [2] http://symfony.com/blog/transition-from-symfony-2-7-to-3-0-symfony-2-8-on-it...
On Wed, Dec 9, 2015 at 8:38 AM, François Kooman fkooman@tuxed.net wrote:
On 12/09/2015 06:17 AM, Neal Gompa wrote:
According to the Symfony website, version 2.8 is the LTS version[1], so why 2.7?
It seems 2.7 is also a LTS version.
Symfony 2.7 is a long term support version with 3 years support that was published in May 2015.
May 2018 End of support for bug fixes
Cheers, François
php-devel mailing list php-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/php-devel@lists.fedoraproject.org
On Wed, Dec 9, 2015 at 8:00 PM, Shawn Iwinski shawn.iwinski@gmail.com wrote:
Correct... 2.7 is also a LTS version [1][2]. It was originally planned to be the last 2.x release as well as the last 2.x LTS version. See [2] for where 2.8 came from.
Not many of my packages use/require 2.8 though so my current plan is to stick with 2.7. We can discuss 2.8 if it is needed though.
[1] http://symfony.com/roadmap?version=2.7#checker [2] http://symfony.com/blog/transition-from-symfony-2-7-to-3-0-symfony-2-8-on-it...
On Wed, Dec 9, 2015 at 8:38 AM, François Kooman fkooman@tuxed.net wrote:
On 12/09/2015 06:17 AM, Neal Gompa wrote:
According to the Symfony website, version 2.8 is the LTS version[1], so why 2.7?
It seems 2.7 is also a LTS version.
Symfony 2.7 is a long term support version with 3 years support that was published in May 2015.
May 2018 End of support for bug fixes
Cheers, François
If you're already making the effort to upgrade to 2.7, you should go ahead and bump to 2.8, because it will make it easier for people to make the move to 3.2 later. If people wind up developing applications against 2.8 as opposed to 2.7, it'll be far smoother because they'll have all the 3.0 features, too. From what I understand from the blog post, 3.0 differs from 2.8 only in that all the deprecations have turned into removals and the compatibility layers are gone. It would make sense to have it make it easier for them to move to 3.2, right?
2.8 is not even in rawhide and many packages are not even verified with 2.8 -- including Drupal 8 [1] which I will be packaging soon.
[1] http://cgit.drupalcode.org/drupal/tree/core/composer.json
On Wed, Dec 9, 2015 at 8:38 PM, Neal Gompa ngompa13@gmail.com wrote:
On Wed, Dec 9, 2015 at 8:00 PM, Shawn Iwinski shawn.iwinski@gmail.com wrote:
Correct... 2.7 is also a LTS version [1][2]. It was originally planned to be the last 2.x release as well as the last 2.x LTS version. See [2] for where 2.8 came from.
Not many of my packages use/require 2.8 though so my current plan is to stick with 2.7. We can discuss 2.8 if it is needed though.
[1] http://symfony.com/roadmap?version=2.7#checker [2] http://symfony.com/blog/transition-from-symfony-2-7-to-3-0-symfony-2-8-on-it...
On Wed, Dec 9, 2015 at 8:38 AM, François Kooman fkooman@tuxed.net wrote:
On 12/09/2015 06:17 AM, Neal Gompa wrote:
According to the Symfony website, version 2.8 is the LTS version[1], so why 2.7?
It seems 2.7 is also a LTS version.
Symfony 2.7 is a long term support version with 3 years support that was published in May 2015.
May 2018 End of support for bug fixes
Cheers, François
If you're already making the effort to upgrade to 2.7, you should go ahead and bump to 2.8, because it will make it easier for people to make the move to 3.2 later. If people wind up developing applications against 2.8 as opposed to 2.7, it'll be far smoother because they'll have all the 3.0 features, too. From what I understand from the blog post, 3.0 differs from 2.8 only in that all the deprecations have turned into removals and the compatibility layers are gone. It would make sense to have it make it easier for them to move to 3.2, right?
-- 真実はいつも一つ！/ Always, there's only one truth!
php-devel mailing list php-devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/php-devel@lists.fedoraproject.org
php-devel@lists.fedoraproject.org
-
François Kooman -
Neal Gompa -
Shawn Iwinski