Hi
I think we should either remove the repo gem5-stable or put in place some
policy regarding gem5-stable. As of now, there is nothing stable about it.
If we want to keep it, I suggest that we do the following:
a. update gem5-stable to gem5 every four months or so. Before updating,
there would be a lean period of say 2-3 weeks when only bug-fixes would be
committed to gem5. At the end of the period, gem5-stable would be updated
to gem5. I propose updating gem5-stable on February 15th, June 15th and
October 15th every year. We can have lean periods starting from 1st
February, 1st June and 1st October.
b. all patches that are committed to gem5 should be evaluated by
developers as to whether they are bug fixes or not. If they are, and the
bug is also present in gem5-stable, then those patches should also be
committed to gem5-stable. I expect the extra work, in most cases, would be
limited to applying the patch to gem5-stable and running the regression
tests.
--
Nilay
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev
