This would a the following benefits:
* Developers would have a certain grace period to fix silly mistakes (like forgetting to check in a header file) without the inevitable "CVS is broken" posting to the users list
* Whenever a developer wants to commit unstable code (f.ex. the MySQL connection pooling code), he could submit it on a tuesday and be finished by the time the stable tag gets applied
* When a major update is being worked on, Isaac (or whoever owns the cronjob) could temporarily hold the stable tag back until everyone working on the upgrade is satisfied that the new code is stable.
* Those that offer RPM packages of CVS snapshots could switch to the stable tag and only update their packages once a week.
* Minimum overhead. Just add a "cvs tag" command to a crontab and forget about it.
The biggest benefit (IMHO) would be psychological. Many other projects offer stable and bleeding branches, and just because the developers work hard to keep the CVS version stable, people would feel better knowing that they are given a choice.
Regards, Eggert
_______________________________________________ mythtv-dev mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
