> Maybe create a new target (since we stopped doing release 2.0bX is kinda > pointless, although I can't come up with anything better).Perhaps the > target release should be date based, quarterly? 3Q2010? Anything that isn't > targeted for a new release date gets offed? > > Along the same lines, we should either update or delete the m5-stable > repository
I think that we should update stable, and that we should also give each stable version a version number so we know what people are using. I propose that the next version stable version is 2.1 (we'll just pretend that 2.0 actually happened some date in the past.) By tagging the latest version (and perhaps putting the version number in a file), we can compile the version number into the binary for easier identification for bug purposes. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
