[Seaside-dev] Seaside 3.0a6ish

[Michael Lucas-Smith]

On 5/19/10 1:52 PM, Julian Fitzell wrote:
> I'm too exhausted to dig into this any further than reading it right 
> now. What Michael's talking about sounds fairly reasoned, but even 
> assuming everyone agrees, I think this is a disruptive change to throw 
> in at this point. What's the smallest change we can make to get it 
> working "good enough" for now?
>
> My suggestion is that... no, crap, that doesn't work at all. I was 
> going to suggest we take the sprint at ESUG to focus on sorting out 
> encoding/decoding (I'd like to be a focus for 3.1 anyway). But since 
> Philippe won't be there and Lukas may or may not be, that's not really 
> going to work out. :)
>
> Ok, so I'm not sure when we tackle that, but the question is still 
> what can we do now that won't make us even *less* likely to release?
We have some tests failing - but a working system.

The tests right now are a curious blend of pragmatism and ideal in this 
case. They exist to demonstrate what the system should do, but are 
implemented in terms of what it can do. In that sense, I do not feel as 
though there is a great urgency in resolving this issue and to fix it at 
this point would mean I could not include 3.0a6 in to VisualWorks 7.7.1 
- it'd have to wait for the next release.

My inclination is to accept these test faults as known and fix up the 
encoding/decoding across smalltalks in the next iteration. In a sense, 
my suggestion is to do nothing for now for 3.0, but to revisit this soon 
after.

Michael