On Thu, Mar 05, 2009 at 07:38:23AM -0600, Patrick R. Michaud wrote:
> On Wed, Mar 04, 2009 at 03:09:57PM -0800, Allison Randal wrote:
> > So, rather than adding "run the tests for X HLLs" to the release
> > process, I'd like to add "check with Y HLL project leads for any release
> > blockers" a couple of weeks in advance of the release. It puts the
> > testing burden back on the language developers, but also makes sure we
> > verify the languages before making the release. Sound workable?
>
> I think a check needs to be done much closer to the release
> date than "a couple of weeks". Either that or we need to do some
> level of "code freeze" between the time of checking with project leads
> and the release. Otherwise we continue to have a good potential for
> the situation that gave rise to this issue in the first place.
Is it practical to automate this? Build a smoker that
0: updates to the HEAD parrot source, and verifies that it passes all tests
(else bail out), and installs that
foreach language
1: update to its HEAD source, and verify that it passes all tests.
(I'm here assuming that languages h by default bundle a parrot, or have a
version control command to retrieve their preferred known good version)
2: clean the language tree, and rebuild against the installed HEAD parrot
3: validate that tests results are identical to step 1.
and then mail a happy summary of "I tried languages X Y Z and all is well"
if nothing goes wrong.
Nicholas Clark
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
