--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscribe@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/52719F5C.9050709%40garfieldtech.com.
For more options, visit https://groups.google.com/groups/opt_out.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CANAnSg2dJJoYK8jU%3DROBnXfa%3D3%3DVrWrTNGsSiphsF-BDuzTxXA%40mail.gmail.com.
I think before we get too deep into this, we should engage the Wordpress guys. Andrew Nacin did a great presentation at php|tek this past spring, which while it was received with a bit of hostility, it really spoke well to folks on the other side of the issue in the "I don't care which version of PHP I'm using as long as things just work".
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CANAnSg3_rwR7pUpzcXb_CPLBkSZg-%2BJDCid8M26UZW-RaXOG6A%40mail.gmail.com.
On 31 October 2013 00:38, John Mertic <jme...@gmail.com> wrote:
I think before we get too deep into this, we should engage the Wordpress guys. Andrew Nacin did a great presentation at php|tek this past spring, which while it was received with a bit of hostility, it really spoke well to folks on the other side of the issue in the "I don't care which version of PHP I'm using as long as things just work".
If Wordpress committed it would be a slam dunk...\
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/5271E550.5020005%40rotorised.com.
The reason we've followed the hosts rather than leading is that wealways believe in maximum compatibility (as I believe Nacin spoke about
at php|tek). If we release versions of WP that require newer versions,
we're leaving users behind who will be unable to upgrade, and that's
much worse to us.
In addition, to my knowledge, there's no really compelling features that
make us want 5.3+. Anonymous functions don't work well with our callback
system (since you can't deregister them later), our classes aren't
suddenly going to change to namespacing (huge backwards compatibility
break if so), etc.
As much as I'd love to push for this personally, I don't think WordPress
is going to get behind this.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/5271C6C5.5050907%40rotorised.com.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CA%2BGmM%3Dxaqf2nN-H0Wjhe7DznM9T1%3DAU8U517NX%3D%2B0aUS6yQzaw%40mail.gmail.com.
Given the different landscape, perhaps a coordinated effort to document
and publicize aggressive upgrade schedules rather than one globally
unified upgrade schedule would be sufficient? That wouldn't have the
big-splash effect of the original GoPHP5, but could have enough of an
effect that we could all move to PHP 5.4 sooner, at the very least.
PyroCMS will also be releasing 2.3.0-alpha1 shortly which ups requirements to PHP 5.3.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/0C9D82B2-EF25-45C8-AD15-3382FC803190%40localheinz.com.
Could FIG also provide upgrade guides? Like an official doc that can help people not familiar with Linux repos / manually compiling the source themselves...
PHP's more aggressive release cycle means we need to move a bit faster
to keep up.
My idea was to set the minimum PHP version to 5.4, not because I am using 5.4 features, but rather to *invite* people to upgrade to 5.4 and above. Is that bad?
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CADyq6s%2BCZf18R5j5YyUXotjr49tLrWpFBYMr-sGryV%2BzhaoCPQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAESZFtJGcSyDjEu%3DLvyB2dcOyWVORVkXFY71aEs9U9yu%3DEW8tQ%40mail.gmail.com.
Hey William DURAND,
I noticed the repo issue. I feel you are wrong in it. If you are not using any of the 5.4 features then there is no need of forcing people.
What is the gain you are seeing ?
You will loose most of the people who are looking for a 5.3 one :)
My 2 cents.
http://harikt.com , https://github.com/auraphp , http://www.linkedin.com/in/harikt , http://www.xing.com/profile/Hari_KTSkype : kthari85Twitter : hariktOn Thu, Jan 23, 2014 at 9:20 PM, Marco Pivetta <ocra...@gmail.com> wrote:On 23 January 2014 16:49, William DURAND <william...@gmail.com> wrote:My idea was to set the minimum PHP version to 5.4, not because I am using 5.4 features, but rather to *invite* people to upgrade to 5.4 and above. Is that bad?Nope, it's a good thing :-)As already discussed with other folks in the past, if people stick with older versions "because stability", they will get the "stability" of no new features ;-)
--To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CADyq6s%2BCZf18R5j5YyUXotjr49tLrWpFBYMr-sGryV%2BzhaoCPQ%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAESZFtJGcSyDjEu%3DLvyB2dcOyWVORVkXFY71aEs9U9yu%3DEW8tQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CALtuQzAOAFOSHYyJBs%2BQqjFgUFpuwc3%2Bfm5jafGeuqJkd1vvow%40mail.gmail.com.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/52E14A51.9030308%40gmail.com.
What is the gain you are seeing ?The _possibility_ to use 5.4-features.
Ever tried to upgrade such a dependency _after_ release? Once you decide for a version you are stuck with it for a while, because else you will probably break existing setups. I've seen this in PR-comments, when Symfony2-bundles dropped their 2.1-support (and that isn't even an interpreter)
Hey,
What is the gain you are seeing ?The _possibility_ to use 5.4-features.In aura, we have always tried to push people to 5.4. But some of the packages can be 5.3 compatible for it only uses short array. What happened is people started forking and keeping them. And many of them asking for the same.
So for v2, we decided to push 5.3 if it can work on 5.3 ( if we don't really need all the traits and stuffs like that which are in 5.4 )
This also reminds me of https://github.com/padraic/mockery/issues/237 (and the network of resulting PRs and calls on Dave’s time). While I do appreciate the HHVM team taking time to fix HHVM, I get a wee bit uncomfortable when it also involves changing Mockery itself (using its developers' free time). Is Facebook benchmarking HHVM’s progress in reaching PHP parity, or the projects’ progress in reaching parity with HHVM?
In any case, my point is that I’m worried about polluting PHP. With PHP 5.6 alpha1, we now have 5 different PHPs to test on. Next there will be 6. Then 7. What is the acceptable gap between the PHP users demand and the PHP that actually exists for us to use? 8?
So, PHP 5.3 needs to die. We’re not doing users any favour in constantly enabling their bad habits and we’re certainly not doing ourselves any either.
--
You received this message because you are subscribed to the Google Groups "PHP Framework Interoperability Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to php-fig+u...@googlegroups.com.
To post to this group, send email to php...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/a32e1f7c-7374-423b-8e27-b0c224850e5a%40googlegroups.com.
I don't think it helps the userland to keep supporting dead PHP versions.--William Durand | http://www.williamdurand.fr
PHP's more aggressive release cycle means we need to move a bit faster