That's an interesting idea. Could it conflict with SemVer + LTS?
--
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/ad7fdaa2-ab6f-4673-a626-f0efb7b76e87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/CAD%3DSCN455sb9-ZYX-Fm2%3D%3DYzkBcaOOZOSkVgpYmo5ptaq2Vmfw%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/55D6B116.2070409%40garfieldtech.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/php-fig/55D6B116.2070409%40garfieldtech.com.
What I would propose is something similar to the security process PSR
that is being discussed: A version support "Best practices" doc that
projects could declare they follow. That would include, I expect, two
key things:
1) The amount of time after a new PHP release comes out that a project
has before it should fully support it (ie, not break on it).
2) The amount of time after a new PHP release is deprecated by Internals
that a project has before it gives up supporting it.
--
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/55D77530.8090306%40garfieldtech.com.
A few small things:1) WordPress the trademark is owned by the WordPress Foundation and WordPress the software is built by a large community. There is no company that is WordPress and thus there is no company that could be funded by EIG.
2) Members of the WordPress community have been actively working with hosts to encourage them to upgrade to more modern versions of PHP. This effort is ongoing.
A few small things:1) WordPress the trademark is owned by the WordPress Foundation and WordPress the software is built by a large community. There is no company that is WordPress and thus there is no company that could be funded by EIG.
--
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/69b81c49-e6ec-4157-85ed-ba914968b770%40googlegroups.com.
1) Who would be willing to Sponsor/Coordinate?
--
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/55D6830A.5080304%40garfieldtech.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/1dba6ab8-cbf4-4b96-b4cb-31ff14d1d120%40googlegroups.com.
phpBB and I suspect other web apps have mechanisms to prevent installation on systems that don't match requirements and the library equivalent is requiring a php version in your composer.json. But I do see what you mean (saying a minimum requirement as opposed to it actually being a minimum requirement).
--
Thanks,
Michael Cullum
--
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/cdcc9055-55bc-4fb3-9836-d805bda770d4%40googlegroups.com.