[Seaside-dev] Seaside 3.1 release?

[Paul DeBruicker]

I'd like to update the ConfigurationOfGrease and 
ConfigurationOfSeaside30 on Squeaksource.com/Seaside31 to the attached 
versions which just reference the most recent packages for both.  Should 
I be added as a Seaside dev?

I set up a travisci.org test for the ConfigurationOfGrease here:

https://travis-ci.org/pdebruic/ConfigurationOfGrease

The github repo is here:
https://github.com/pdebruic/ConfigurationOfGrease

The Grease 'Slime Tests' fail on Pharo 1.4 so I've just set travisci to 
load and run the Grease 'Core Tests' for now.  Right now the 
ConfigurationOfGrease tests are running against all the platforms, and 
ConfigurationOfSeaside30 is still just Pharo-1.3.







On 11/11/2012 08:48 AM, Paul DeBruicker wrote:
> On 11/10/2012 12:57 PM, Philippe Marschall wrote:
>> On Sat, Nov 10, 2012 at 5:17 PM, Paul DeBruicker<pdebruic at gmail.com>
>> wrote:
>>> >In May there was a discussion about getting the 3.1 configuration
>>> ready for
>>> >release.  Did that get completed or is there a list of tasks
>>> somewhere that
>>> >I could work on to move it forward?
>> We reworked the configuration at ESUG but it depended on a not yet
>> release version of Monticello. Then Dale did a release of Monticello
>> and some updates to the configuration. It's completely my fault that I
>> haven't yet found the time to test the configuration of the new
>> version of Monticello. What you can do to help, test the
>> configuration. You'll have to use ConfigurationOfSeaside30, not
>> ConfigurationOfSeaside31. For backwards compatibility reasons we
>> decided to keep it named ConfigurationOfSeaside30. If you look at the
>> class comment and the baselines-31 protocol you'll see that it has
>> been reorganized into several groups. Basically everything has an
>> accordingly named group. So we have many more, much more fine grained
>> groups.
>>
>> So you'd do something like
>>
>>     (ConfigurationOfSeaside30 project version: '3.1.0)
>>       load: #('Core' 'JQuery' 'Kom')
>
>
> Ok.  I've made a ConfigurationOfSeaside30 repo on github here:
>
> https://github.com/pdebruic/ConfigurationOfSeaside30
>
> and, for now, set it up use travisci.org to load and run the core
> seaside packages in Pharo 1.3.  It hasn't succeeded yet but its giving
> some feedback you can see here:
>
> https://travis-ci.org/pdebruic/ConfigurationOfSeaside30
>
> I intend to attempt to automatically make branches to test each
> interesting combination of Seaside package loads on each intended
> supported platform among these possible platforms:
>      PharoCore 1.1, 1.2, 1.3
>      Pharo 1.4, 2.0
>      Squeak 4.3, 4.4
>
> I'm not sure what those interesting combinations of packages are and am
> reluctant to just make the Travisci.org service test the complete of all
> combinations of all groups provided by 3.1 baselines.
>
>
> My questions are:
>
>      1.  What are the platforms Seaside 3.1 is supporting
>      2.  Is there a list of sets of packages to load and test that are
> more interesting than others that I should start making branches for?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfGrease-PaulDeBruicker.190.mcz
Type: application/octet-stream
Size: 34456 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20121111/63c47792/ConfigurationOfGrease-PaulDeBruicker.190-0001.obj
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ConfigurationOfSeaside30-PaulDeBruicker.410.mcz
Type: application/octet-stream
Size: 150099 bytes
Desc: not available
Url : http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20121111/63c47792/ConfigurationOfSeaside30-PaulDeBruicker.410-0001.obj