[squeak-dev] GitHub issues filed for Seaside load warnings in Squeak 6.0 beta
marcel.taeumel at hpi.de
Thu Jun 9 09:25:23 UTC 2022
Hi Tobias --
If we want to ensure some kind of modularity with our deprecations, jumping to 70Deprecated would be a very bad idea. We did this with 60Deprecated and it's a mess.
Again, version numbering or package naming has nothing to do with the decision to opt-in or opt-out to certain deprecated stuff.
Am 09.06.2022 11:23:01 schrieb Tobias Pape <das.linux at gmx.de>:
> On 9. Jun 2022, at 10:59, Marcel Taeumel wrote:
> Hi Tim --
> Interesting. So, would it really make sense to have 60Deprecated already loaded in the release image? I think it would be better to fix these issues. At least in 6.1, I do not want to have 60Deprecated loaded anymore by default. People should opt-in for that.
make that 7.0 not 6.1 ;P
>> Am 05.06.2022 02:50:36 schrieb Tim Johnson :
>> Hi all,
>> Just FYI —
>> I went through loading Seaside in 6.0beta-#21848. (Metacello loading is so fast now! Great job and thank you!)
>> There are two places where the BlockContext family retirement will break Seaside loading. One is a rendering method but the other is in continuations. I've filed issues on the Seaside GitHub project. It's clear that if we want these fixed, we will have to do it ourselves.
>> BaselineOfSeaside3>>#baselinesqueak: would be a good place to begin splitting out the new requirements for Squeak 6.0 compared to earlier versions. I don't know that /this/ list is the proper place to have much discussion about this, but I thought I'd mention it here.
>> Tim J
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Squeak-dev