<div dir="ltr"><font color="#330033"><font size="2"><font face="tahoma,sans-serif">So we have two issues:<br>1) Functional tests - can we, or can't we automate these? even if a large portion can be automated, how do you think this should be done?<br>
2) Should we have a Grease-only build? (Dale's suggestion)<br><br>Regarding suspending the commits until a release - this works only because we're a small community :)<br>I would definitely go for an automated build system which can handle both: (a) taking the latest package versions and doing nightly builds; and (b) defining a set of packages (or a Metacello configuration) for a release, and building it regardless of new commits (whether through a dedicated Hudson Seaside build, or some other mechanism).<br>
<br>Another issue:<br>Dale, Do we build/update/run a new release under each and every dialect manually?<br>If it's manual, then maybe there's room for a script that fetches a Metacello configuration and runs Seaside tests against all dialects? or possibly a few dialect-specific scripts that automate this?<br>
<br><br>Avi.<br></font></font></font><br><div style="margin: 0pt;" name="sig_d41d8cd98f"></div><div class="gmail_quote">On Sun, Mar 6, 2011 at 6:48 PM, Julian Fitzell <span dir="ltr"><<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">On Sun, Mar 6, 2011 at 2:19 PM, Philippe Marschall<br>
<div class="im"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>> wrote:<br>
</div><div class="im">> 2011/3/5 Avi Shefi <<a href="mailto:avishefi@gmail.com">avishefi@gmail.com</a>>:<br>
</div><div class="im">>> We can make the build process less involved.<br>
><br>
> Having it done several times I really feel that manually running the<br>
> functional tests is the biggest issue.<br>
<br>
</div>Agreed. Everything else is now automated enough that it's not too much<br>
hassle. The functional tests are a big pain...<br>
<br>
Which is not to say they should be got rid of, because they are useful<br>
examples to exercise specific functionality when you are developing<br>
and want to try things out. But it would be nice to to rely on them to<br>
verify builds.<br>
<font color="#888888"><br>
Julian<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>