[Seaside-dev] [Seaside] Build Process

[Lukas Renggli]

Yes. We probably stop to produce 2.8 builds soon, as Magritte and Pier
(and most other open-source projects) are sucessfully running on
Seaside 3.0. Also there has been no new changes in the 2.8 branch
lately.

Lukas

On Thursday, 10 March 2011, Avi Shefi <avishefi at gmail.com> wrote:
> Just looked at the Jenkins (previously Hudson) build server, and saw that there are separate tabs for Seaside 2.8 and Seaside 3.0.
> Does this mean that we have separate builds for each one?
>
> Avi.
>
> On Tue, Mar 8, 2011 at 10:03 PM, Dale Henrichs <dhenrich at vmware.com> wrote:
> On 03/08/2011 10:42 AM, Lukas Renggli wrote:
>
>
> You are already doing the #bleedingEdge builds, so that would only be useful
> from the perspective that Metacello will flush out dependency bugs that the
> current build process doesn't uncover. It would be nice if there were
> continuous development builds for all of the supported Pharo versions
> (whatever the list is) and adding Squeak builds would be nice, too.
>
>
> It is the responsibility of the respective stakeholders to keep their
> ports up-to-date. Different Hudson/Jenkins instances can interoperate
> with each other, so we could combine the results of all build servers
> at a central location. However, I am not willing to maintain builds
> for platforms I don't care about.
>
>
>
> That's fine...it _was_ worth mentioning though:)
>
>
>
>
> The most useful from my perspective would be a #stable build. The stable
> build could be used to produce the Pharo release artifacts: image, changes,
> on-clicks based on the configurations...Right now there is potential for
> discrepancies between the configurations and the release artifacts....With a
> hudson build using the confg there'd be no discrepancies.
>
>
> I think it would make sense to have a parallel "stable" Metacello
> based build that updates whenever the Metacello configuration changes.
>
>
>
> That would be excellent!
>
>
>
>
> Pharo builds the stable Seaside release on Pharo1.2 only which AFIAK isn't
> supported by Seaside30 yet...
>
>
> I don't think Pharo 1.2 stable is out yet, or did I miss something?
>
>
>
> I was referring the the #stable version of Seaside30, not Pharo, sorry.
>
>
>
> My Jenkins instance uses
> http://www.pharo-project.org/pharo-download/stable which still points
> to Pharo 1.1. As soon as this changes we will likely have to fix a few
> things.
>
> Also note that Pharo itself has several builds (that include Seaside)
> that are based on their development images:
> https://pharo-ic.lille.inria.fr/hudson/view/Pharo-Clients/
>
>
>
> Right and those are all built against Pharo 1.2 and Seaside30 isn't supported on Pharo 1.2 yet ...
>
>
> Dale
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
>
>

-- 
Lukas Renggli
www.lukas-renggli.ch