Hi,
I wonder if there is any objection to this plan:
- enable phar by default for the PHP 5.3 betas, so that it can receive
full testing - before RC1, do the formal vote on whether it should be enabled by
default in the release
This way, phar can be tested for the possibility of enabling, but there
is an explicit safety net in place should it need reconsidering.
My assumption here is that there will be a few beta releases and
possibly an alpha release or two prior to the first RC.
Thanks,
Greg
Go for it, we can always change our mind before the vote if something
comes up.
Scott
Gregory Beaver wrote:
Hi,
I wonder if there is any objection to this plan:
- enable phar by default for the PHP 5.3 betas, so that it can receive
full testing- before RC1, do the formal vote on whether it should be enabled by
default in the releaseThis way, phar can be tested for the possibility of enabling, but there
is an explicit safety net in place should it need reconsidering.My assumption here is that there will be a few beta releases and
possibly an alpha release or two prior to the first RC.Thanks,
Greg
Gregory Beaver escribió:
Hi,
I wonder if there is any objection to this plan:
- enable phar by default for the PHP 5.3 betas, so that it can receive
full testing- before RC1, do the formal vote on whether it should be enabled by
default in the release
Make sense, otherwise it wont be tested at all.. +1 although I dont
think we need phar in the core, but something more useful like pecl_http
or fileinfo instead.
--
"Progress is possible only if we train ourselves to think about programs
without thinking of them as pieces of executable code.” - Edsger W.
Dijkstra
Cristian Rodríguez R.
Platform/OpenSUSE - Core Services
SUSE LINUX Products GmbH
Research & Development
http://www.opensuse.org/