[php-maint] php 5.3.1 in experimental

sean finney seanius at debian.org
Fri Feb 5 16:18:11 UTC 2010

hi everyone,

On Fri, Feb 05, 2010 at 09:42:33AM -0600, Raphael Geissert wrote:
> I did that more than a week before. At the moment we must wait for the
> RT to give us the green light before uploading to sid as it is
> considered a transition (the phpapi was bumped and needs binNMUs) and
> the buildds are overloaded.

is there anything missing from our end on this?  otherwise i say we get
pretty aggressive about pushing this as i absolutely do not want to get
stuck with having 5.2.x in squeeze.

> I was thinking maybe we should upload one more version to experimental
> and send the "bits from" email so that people start using it. What do
> you think?

I say skip this step, as we've had 5.3 in experimental for quite a while
already and people have had their chance to object.

> I also wanted to discuss, again, the changes to php.ini. At the moment
> you added code to debian/rules to change the short_open_tag setting
> but maybe we should not modify any of the settings for now.

ideally i'd like to stick with upstream on this and have it disabled
by default, but at this point in the release cycle i suspect this change
would be just as disruptive (if not more) than the version/abi bump.  and
more importantly any errors that it introduces would not be immediately
detected and would probably take a while to trickle their way to us.

debian packages and deployed apps/websites that require short_open_tag
to be off already have the setting because otherwise they'd be broken,
so keeping the setting as is doesn't break anything.  changing the
setting will probably break some packages (which we could probably do
something to find/fix) and deployed apps/sites (which we couldn't completely
find/fix).  i'd rather have to deal with something like that at the beginning
of a release cycle rather than just before a freeze.

> The problem is that applications need to be fixed either way, because
> sooner or later that's going to be the default. I also noticed I
> forgot to mention the JIT setting, which might silently break some
> routines of a couple of applications.

which setting is that.. auto_globals_jit?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-maint/attachments/20100205/f9f6c0ea/attachment.pgp>

More information about the pkg-php-maint mailing list