Bug#657077: transition: php5 5.4
On Mon, Feb 6, 2012 at 21:13, Julien Cristau <jcristau@debian.org> wrote:
> On Mon, Feb 6, 2012 at 20:14:53 +0100, Ondřej Surý wrote:
>> 2012/2/6 Julien Cristau <jcristau@debian.org>:
>> > On Mon, Feb 6, 2012 at 14:46:51 +0100, Ondřej Surý wrote:
>> >
>> >> So I would say we are pretty safe on this front. PHP scripts still could
>> >> break in every possible way, but I don't think we would be able to detect
>> >> that easily.
>> >>
>> > Well, there'll need to be *some* way to detect them before release,
>> > surely? Maybe that means testing each php package individually, and
>> > gathering a list of which packages have received successful testing.
>> > The testing could be done by the individual package maintainers, but
>> > it'd be nice if somebody was collecting the results so we know what has
>> > or hasn't been tested.
>>
>> Yes, that can be done. But ... do we do that for other languages?
>> python? perl?
>>
> I'm pretty sure something like that was done for python. I don't think
> perl breaks source level compatibility to anywhere near the same extent
> (could be wrong, though).
Alright.
>> Anyway I'll setup a wiki page and when you ack the php5 5.4 upload, I'll mail
>> the package maintainers and ask them to test their packages individually.
>>
> They can test right now with php from experimental...
How many of them do you think will do that? I am big pessimist here.
Do you think that email about testing with experimental packages now
and then second (well third if you count that in d-d-a) email will not be
too much?
I would rather skip the one with "please test with package in experimental" now
and then push people to really test with php5 in unstable.
O.
--
Ondřej Surý <ondrej@sury.org>
Reply to: