Absolutely! All of us will make mistakes occasionally and commit code that will break the tests (either because they have not been run or because the environment is different). In this case a good developer would look into IRC to alert the committer in question.
On 21.09.2011, at 08:53, Christoph Drießen wrote: > +1, since broken revisions aren't acceptable. > When a committer rolls back a commit from someone else, is he supposed to > notify that respective person? If the bug can be fixed in a timely manner then it doesn't make sense to roll anything back. Timely manner however should (in my opinion) be defined as an hour or two, certainly not a day. The idea of these tests are, that * developers can be sure to update to something that will at least build and contain the functionality that was there yesterday, in a working state. * QA doesn't have to test just *everything*, and we can ensure a certain degree of functionality simply by running the integration tests. Tobias _______________________________________________ Matterhorn mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn To unsubscribe please email [email protected] _______________________________________________
