Seaside 3.2.0 for Pharo 1.x ?

> On 23 Jul 2015, at 13:51, Philippe Marschall <[hidden email]> wrote:
>
>> On Thu, Jul 23, 2015 at 11:30 AM, Johan Brichau <[hidden email]> wrote:
>> Hi,
>>
>> Do we still want to support loading Seaside 3.2.0 in Pharo1.x ?
>> Configuration management is getting overly complex _and_ some packages (Welcome, Rest, Slime, etc… are not being updated anymore for that platform).
>>
>> Opinions?
>
> I'm still on 1.3 but I'm probably the only one. I would be fine if the
> configuration no longer supports 1.x and anybody who still wants to
> use 1.x would be on this own.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

> On 24 Jul 2015, at 12:47, Philippe Marschall <[hidden email]> wrote:
>
> On Thu, Jul 23, 2015 at 6:28 PM, Johan Brichau <[hidden email]> wrote:
>> Ok, for now I did not explicitly remove those sections, but I will be working on a new configuration baseline and drop them there. Probably that's for 3.3 though.
>>
>> Btw, testContentsNotifying is failing since the latest changes.
>>
>> I'll take a look at the failing swagger tests now
>
> I fixed some of them (mostly missing Metacello dependencies) but two
> still fail. I added some more debug info in case of failures (it could
> be that we rely on a not guaranteed method order) but it seems to me
> as if #version320: is running into a literal limit.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev