Patrick R. Michaud wrote:
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.
A couple of days? The longer time-frame was to give language devs time
to report failures so we could fix them.
Daily or even weekly smokes of a language against parrot trunk would be
ideal, but I'm balancing that against reasonable human effort. Is one
run mid-month, and one just before the release manageable?
Allison
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
