In my opinion it is necessary to have some sort of review policy, if we
want to keep our developers together (which we all do, I think). While
fixing the testsuite and having things compile are very useful, it does
not solve the problem of (tree-wide) code quality degradation. I think a
review policy could solve most of that problem. Such a policy would be
especially important where large-scale changes are contemplated.
Bastiaan
On Fri, 21 May 2010, John Gilmore wrote:
* We figure out why Rob's pre-checkin test runs are not showing
things that Benjamin's post-checkin test runs make obvious.
* We keep the tree compiling and passing its test suite almost
every day.
* If we have really made youtube usable with the hacks and kludges
about plugin reporting of version numbers, etc, then I hope we
can cut a release sometime soon, so the distros can pick it up as
an update and make gnash usable for the most popular video site.
_______________________________________________
Gnash-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnash-dev
