On Sun, Jun 15, 2008 at 8:19 PM, nathan binkert <[EMAIL PROTECTED]> wrote: >> What about something along the lines of the following: The m5-stable >> repository gets updated at a regular interval (1 month works for an >> example and it seems like a reasonable time frame to me). Instead of >> coming up with some conditions when m5-stable is updated from m5 >> automagically, we also impose a schedule on committing to the m5 >> repository. For example for the first 15 days of each month, any >> patches that pass regressions and the committer has tested and >> believes work can be committed. For the next week only minor changes >> can be committed, and finally for the forth week of each month only >> bugfixes can be committed. On the last day of the month the repository >> should be rather stable. Any largish changes would have been tested >> for 2 weeks. >> >> In the case of some bug fix that needs to be released immediately that >> fix could be pushed directly to m5-stable and pulled into m5. > This is an intriguing idea. OpenBSD does this on a 6 month schedule > and it works pretty well. Several other groups (ubuntu for example) > have also started on doing this. 6 months would be way too much for > us, but I think on this shorter schedule, it might be doable.
Yea, I like this too. > It > seems that certain things (like x86) ought to be exempt from this rule > though. Why? I'd rather establish exceptions when the need becomes apparent rather than up front. > > The big issue is collaboration among people (like me and steve) and > how we need to do that, but I guess with mq and local repositories, > we've got enough tools. I'm sure we could work it out as needed. Steve _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
