builds for pharo 4?

Hi,

Does it make sense to set up a build process for Seaside on a Pharo version that is known to be unstable and evolving?

If the Pharo 4 we build on is unstable, it does not make sense to test Seaside on it.

Is there a way to only use a stable build of Pharo 4?

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

Johan wrote:
>Does it make sense to set up a build process for Seaside on a Pharo version that is known to be unstable and evolving?

Yes. We'd like pharo developers to know when they break seaside. (and pier, magritte, and grease).

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

On 10 Jun 2014, at 12:39, Stephan Eggermont <[hidden email]> wrote:

> Johan wrote:
>> Does it make sense to set up a build process for Seaside on a Pharo version that is known to be unstable and evolving?
>
> Yes. We'd like pharo developers to know when they break seaside. (and pier, magritte, and grease).

Ok, but do they look at it?
Or is it just us who get spammed? :-)

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

The concepts “stable” and “Pharo 4” are incompatibles right now :)
Even if now is not really divergent from Pharo 3 (and I think is working very stable), is a development version… even worst, is not even an alpha.
And it will be like that during some months… I wouldn’t bet on his stability for now.

cheers,
Esteban

On 10 Jun 2014, at 06:31, Johan Brichau <[hidden email]> wrote:

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

On Tue, Jun 10, 2014 at 2:50 PM, Esteban Lorenzano <[hidden email]> wrote:
> The concepts “stable” and “Pharo 4” are incompatibles right now :)
> Even if now is not really divergent from Pharo 3 (and I think is working very stable), is a development version… even worst, is not even an alpha.
> And it will be like that during some months… I wouldn’t bet on his stability for now.

Is there a way I don't get failure emails for Pharo 4 other than
setting up a rule in my user agent?

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

On 10 Jun 2014, at 15:40, Philippe Marschall <[hidden email]> wrote:

> On Tue, Jun 10, 2014 at 2:50 PM, Esteban Lorenzano <[hidden email]> wrote:
>> The concepts “stable” and “Pharo 4” are incompatibles right now :)
>> Even if now is not really divergent from Pharo 3 (and I think is working very stable), is a development version… even worst, is not even an alpha.
>> And it will be like that during some months… I wouldn’t bet on his stability for now.
>
> Is there a way I don't get failure emails for Pharo 4 other than
> setting up a rule in my user agent?

It is very useful to have continuous Seaside builds to ensure future compatibility. But right now, because Pharo 4 is just starting its evolution, it is way too early to take the failures very seriously. Hence, sending so many mails around is too much. I would vote for keeping the CI jobs, but sending less or no notifications for those based on 4.0.

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

Making the Pharo 4 build work correctly needs too many steps atm. I'll create a separate build
that doesn't post the mails for now._______________________________________________
seaside-dev mailing list
[hidden email]
http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev