There should be CI job for Roassal2 #stable and Pharo4.
Especially if most of Roassal contributors/devs are in Pharo 5 and thus only end-users will notice it.

(with the multi-configuration job in Jenkins it's easy to setup custom matrix)

Peter

On Fri, Sep 25, 2015 at 11:37 AM, Tudor Girba <tudor@tudorgirba.com> wrote:
Thanks for your patience, Volkert.

And thanks Alex for fixing the configuration.

Cheers,
Doru


On Fri, Sep 25, 2015 at 10:30 AM, Volkert <volkert@komponentenwerkstatt.de> wrote:
On 25.09.2015 07:52, Sven Van Caekenberghe wrote:
On 25 Sep 2015, at 05:18, Volkert <volkert@komponentenwerkstatt.de> wrote:

But how do i figure out, which is the right Version for Pharo 4.0? I always thought loadStable is ok, as mentioned http://objectprofile.com/Roassal.html.
You are right, as an end user you should just use #stable on any supported platform and it should work.

The authors of the configuration can declare for each platform (Pharo 4, 5) which is the stable version.

Obviously someone made a mistake while moving forward, we are all humans after all.
 i have no intention to blame here someone ... i only try to understand how the things  are connected ... and i have learned something new ...

Volkert



_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev



--

"Every thing has its own flow"

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev