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?
Johan
On Thu, Jul 23, 2015 at 11:30 AM, Johan Brichau johan@inceptive.be 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
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
On 23 Jul 2015, at 13:51, Philippe Marschall philippe.marschall@gmail.com wrote:
On Thu, Jul 23, 2015 at 11:30 AM, Johan Brichau johan@inceptive.be 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 seaside-dev@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
On Thu, Jul 23, 2015 at 6:28 PM, Johan Brichau johan@inceptive.be 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.
Fixed.
Cheers Philippe
On Thu, Jul 23, 2015 at 6:28 PM, Johan Brichau johan@inceptive.be 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
I noticed… I just fixed those as well and we committed different versions.
I merged them and published latest one now.
On 24 Jul 2015, at 12:47, Philippe Marschall philippe.marschall@gmail.com wrote:
On Thu, Jul 23, 2015 at 6:28 PM, Johan Brichau johan@inceptive.be 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 seaside-dev@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
On 24 Jul 2015, at 12:47, Philippe Marschall philippe.marschall@gmail.com wrote:
it seems to me as if #version320: is running into a literal limit.
I split the method and committed
Some packages are missing, so we need more.
seaside-dev@lists.squeakfoundation.org
-
Johan Brichau -
Philippe Marschall