[Seaside-dev] Grease 1.0.3 and Seaside 3.03 are poised for release.

[Dale Henrichs]

On 12/13/2010 09:49 PM, Philippe Marschall wrote:
> 2010/12/14 Dale Henrichs<dhenrich at vmware.com>:
>> Seaside3.0.3 has been loaded and tested on Pharo1.0, Squeak4.1, Pharo1.1.1,
>> and GLASS 1.0-beta.8.4...all tests run Green and the Metacello
>> configurations have been marked as released.
>>
>> In going through the steps on the Make Release page:
>>
>>
>> http://code.google.com/p/seaside/wiki/MakeRelease?ts=1291839439&updated=MakeRelease
>>
>> I discovered a handfull of issues which I am detailing here:
>>
>> Step 2.2:
>>   This needs to be automated, there are way too many combinations
>>   to test manually especially if you are interested in releasing often
>>   (tell me how many times has the Swazoo adaptor been tested with
>>   koi8-r encoding (and would I be able to tell if there was a bug)?)
>> Step 4:
>>   I ran the doit ... code executed but I got no feedback good or bad
>>   from running #graphFunctionalDependencies:tests:
>> Step 5:
>>   I click on the link and I get a csv file ... what is supposed to be
>>   done with it? Is this step subsumed by the ChangeLog page?
>> Step 6:
>>   Not sure where the image/changes file is supposed to come from
>>   and I'm pretty sure I don't have permissions to modify any of the
>>   links
>> Step 7:
>>   No access to twitter...
>> Step 8:
>>   Can't update until Step 6 is completed.
>>
>> So in the end, I think we're awfully dang close to releasing 3.0.3 ... the
>> code is ready, but the release artifacts (like the one-click image and
>> website updates haven't been done...).
>
> Just out of curiosity, what about Issue 620? I though this was your
> main driver to do 3.0.3.
>
> Cheers
> Philippe
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Issue 602 was not a driver at all. I have GemStone-specific branch for 
Seaside-Core where I fixed the bug for GemStone (Issue 186). And I just 
plain forgot about 602:)

My drivers for Seaside30 were:

- fix Issue 186: http://code.google.com/p/glassdb/issues/detail?id=186 
"WAFileLibrary>>deployFiles fail if folder already exists" [GemStone]
- fix Issue 169: http://code.google.com/p/glassdb/issues/detail?id=169 
"Incorporate GemStone Futures code from Nick Ager" [GemStone]
- fix Issue 191: http://code.google.com/p/glassdb/issues/detail?id=191 
"getting object log continuation for rest api calls" [GemStone]

plus a slug of base GLASS1.0-beta.8.5 changes that affects the behavior 
of seaside30...

Dale