Smalltalk › Frameworks & Tools › Seaside › Seaside Development

Seaside 3.1 release?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Paul DeBruicker

Seaside 3.1 release?

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?

Has 3.1 been released or is there a date set for releasing 3.1? I ask
because it looks like there hasn't been anything 3.1 related uploaded to
the squeaksource repo since September 3rd.

Thanks

Paul
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Philippe Marschall

Re: Seaside 3.1 release?

On Sat, Nov 10, 2012 at 5:17 PM, Paul DeBruicker <[hidden email]> 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')

and it's pretty clear what you'll get.

> Has 3.1 been released or is there a date set for releasing 3.1? I ask
> because it looks like there hasn't been anything 3.1 related uploaded to the
> squeaksource repo since September 3rd.

Right, I should have tested the configuration but didn't.

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Paul DeBruicker

Re: Seaside 3.1 release?

On 11/10/2012 12:57 PM, Philippe Marschall wrote:

> On Sat, Nov 10, 2012 at 5:17 PM, Paul DeBruicker<[hidden email]> 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?
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Paul DeBruicker

Re: Seaside 3.1 release?

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<[hidden email]>
>> 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?

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

ConfigurationOfGrease-PaulDeBruicker.190.mcz (46K) Download Attachment

ConfigurationOfSeaside30-PaulDeBruicker.410.mcz (200K) Download Attachment

Philippe Marschall

Re: Seaside 3.1 release?

In reply to this post by Paul DeBruicker

On Sun, Nov 11, 2012 at 5:48 PM, Paul DeBruicker <[hidden email]> wrote:

> On 11/10/2012 12:57 PM, Philippe Marschall wrote:
>>
>> On Sat, Nov 10, 2012 at 5:17 PM, Paul DeBruicker<[hidden email]>
>> 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

Ok, I wasn't planning on doing this but I'm not going to argue with
people who do work.

> 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

Right now the most tested ones probably are Pharo 1.3, and 2.0. Pharo
1.4 and Squeak 4.3 should work but aren't really well tested to my
knowledge. More will hopefully be added with time.

> 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?

Core, Development, Omnibrowser, jQuery, Kom and Zinc are probably the
most important ones.

Cheers
Philippe
_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev

Paul DeBruicker

Re: Seaside 3.1 release?

On 11/11/2012 11:35 AM, Philippe Marschall wrote:
> Right now the most tested ones probably are Pharo 1.3, and 2.0. Pharo
> 1.4 and Squeak 4.3 should work but aren't really well tested to my
> knowledge. More will hopefully be added with time.
>
>> > 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?
> Core, Development, Omnibrowser, jQuery, Kom and Zinc are probably the
> most important ones.

On Travis-CI I've gotten the ConfigurationOfGrease and
ConfigurationOfSeaside30 for 3.1 to work on Squeak 4.3 & 4.4 and Pharo
1.3 & 1.4. The download for Pharo 2.0 was broken so I wasn't able to
check it. I only had to make some small changes primarily to the
version #'s of package but also to make Seaside-Session dependent upon
Seaside-Canvas as it has extension methods for some of that packages
classes.

For Seaside 3.1 I've only run the ('Tests') group but they all pass
using the configs in the git repos on the platforms I mentioned earlier.
I have yet to try the other groups you mentioned but should have time
to add them tomorrow eve.

_______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev