Patrick R. Michaud wrote:
I think that a run mid-month and again just before release is manageable.
And I don't think the criteria ought to be "does the language pass all
of its tests" -- it simply needs to be "do the HLL project leads
have any critical blockers for the current trunk that is about to be
released?"
In Rakudo's case, I don't necessarily need Parrot trunk to build
Rakudo without any test failures; but I do need to know that the
about-to-be-released-trunk doesn't contain a fatal flaw that
will prevent Rakudo from building altogether, regardless of any
fixes/updates we might be able to apply to Rakudo.
Yes, that makes sense. I've added some language to the release manager's
guide in r37245. Take a look and let me know what you think.
Thanks,
Allison
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
