2009/6/12 Michael Wallner :
> Matt Wilmas wrote:
>> Hi Dmitry, Antony,
>>
>> Fixed, thanks.
>>
>
>>> Matt Wilmas wrote:
mattwil Wed Apr 1 17:05:37 2009 UTC
Removed files: (Branch: PHP_5_3)
/php-src/ext/standard/tests/strings bug47546.phpt
Modified fil
2008/10/23 Hannes Magnusson <[EMAIL PROTECTED]>:
> On Thu, Oct 23, 2008 at 12:26, Jani Taskinen <[EMAIL PROTECTED]> wrote:
>> Hannes Magnusson wrote:
>>>
>>> On Thu, Oct 23, 2008 at 11:51, Jani Taskinen <[EMAIL PROTECTED]> wrote:
2. You can always simply put a short comment like "Fixed in
On Thu, Oct 23, 2008 at 12:26, Jani Taskinen <[EMAIL PROTECTED]> wrote:
> Hannes Magnusson wrote:
>>
>> On Thu, Oct 23, 2008 at 11:51, Jani Taskinen <[EMAIL PROTECTED]> wrote:
>>>
>>> 2. You can always simply put a short comment like "Fixed in CVS, needs
>>> documenting" and reclassify the bug repo
Hannes Magnusson wrote:
On Thu, Oct 23, 2008 at 11:51, Jani Taskinen <[EMAIL PROTECTED]> wrote:
2. You can always simply put a short comment like "Fixed in CVS, needs
documenting" and reclassify the bug report as docu issue. There's no need
for some fancy shortcuts or such. Just tune your proces
On Thu, Oct 23, 2008 at 11:51, Jani Taskinen <[EMAIL PROTECTED]> wrote:
> 2. You can always simply put a short comment like "Fixed in CVS, needs
> documenting" and reclassify the bug report as docu issue. There's no need
> for some fancy shortcuts or such. Just tune your process..
Well, or use the
Jani Taskinen wrote:
1. This should be applied to PHP_5_2 (not big change and in no way can
break anything)
2. You can always simply put a short comment like "Fixed in CVS, needs
documenting" and reclassify the bug report as docu issue. There's no
need for some fancy shortcuts or such. Just t
1. This should be applied to PHP_5_2 (not big change and in no way can
break anything)
2. You can always simply put a short comment like "Fixed in CVS, needs
documenting" and reclassify the bug report as docu issue. There's no
need for some fancy shortcuts or such. Just tune your process..
-
Allright,
I think we can push an RC1 later on this week and depending on how
well it does move onto the final in the coming weeks. After reviewing
the PHP 5.2 changelog I think it is not unrealistic to get a version
out by the end of the month or early November.
On 6-Oct-08, at 2:27 PM,
On Mon, 2008-10-06 at 14:07 -0400, Ilia Alshanetsky wrote:
> 5.2 necessity depends entirely on the availability dates of PHP 5.3
> and presence of critical fixes that absolutely require a 5.2.X
> release.If Lukas does not see a 5.3 release happening until end of
> November, we can definitely
hi Ilia,
On Mon, Oct 6, 2008 at 8:07 PM, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> 5.2 necessity depends entirely on the availability dates of PHP 5.3 and
> presence of critical fixes that absolutely require a 5.2.X release.If Lukas
> does not see a 5.3 release happening until end of November,
On Mon, Oct 6, 2008 at 20:07, Ilia Alshanetsky <[EMAIL PROTECTED]> wrote:
> 5.2 necessity depends entirely on the availability dates of PHP 5.3 and
> presence of critical fixes that absolutely require a 5.2.X release.If Lukas
> does not see a 5.3 release happening until end of November, we can
> de
5.2 necessity depends entirely on the availability dates of PHP 5.3
and presence of critical fixes that absolutely require a 5.2.X
release.If Lukas does not see a 5.3 release happening until end of
November, we can definitely do a 5.2.7 for the end of October...
On 3-Oct-08, at 10:02 AM, Ja
2008/10/3 Lukas Kahwe Smith <[EMAIL PROTECTED]>:
>
> On 03.10.2008, at 16:02, Jani Taskinen wrote:
>
>> PHP 5.2.7 is long overdue already. Propably due to the RM being AWOL for
>> quite long time. There are several fixes in 5.2.7 that should be out there
>> yesterday. If the current RM is not inter
On 03.10.2008, at 16:02, Jani Taskinen wrote:
PHP 5.2.7 is long overdue already. Propably due to the RM being AWOL
for quite long time. There are several fixes in 5.2.7 that should be
out there yesterday. If the current RM is not interested in releases
anymore, I can take over.
I guess
Lukas Kahwe Smith wrote:
On 02.10.2008, at 14:27, Ilia Alshanetsky wrote:
No, its for security or "critical" fixes only. I'd say that a crash
inside a key area of the code is critical...
Hmmh.. Does this mean that 5.2 is dead and all the unreleased 5.2 NEWS
entries should be moved to 5_3?
On 02.10.2008, at 14:27, Ilia Alshanetsky wrote:
No, its for security or "critical" fixes only. I'd say that a crash
inside a key area of the code is critical...
Hmmh.. Does this mean that 5.2 is dead and all the unreleased 5.2
NEWS
entries should be moved to 5_3?
Just to give persp
Hello Greg,
Monday, August 4, 2008, 10:37:23 PM, you wrote:
> Rasmus Lerdorf wrote:
>> Jani Taskinen wrote:
>>> -- Changed PCRE, Reflection and SPL extensions to always be enabled.
>>> (Marcus)
>>> +- Changed PCRE, Reflection and SPL extensions to be always enabled.
>>> (Marcus)
>>
>> That was
17 matches
Mail list logo
