Joshua Spence ef18ae08eb Don't explicitly name abstract base classes ... Summary: Ref T5655. It is superfluous to include "base" in the name of an abstract base class. Furthermore, it is not done consistently within the code base. In order to retain compatibility with external code, I have kept the `ArcanistBaseWorkflow` class (which trivially extends from `ArcanistWorkflow`), but it is now deprecated and should output a warning message. Similarly for `ArcanistBaseUnitTestEngine`. Test Plan: Created a workflow which extends from `ArcanistBaseWorkflow`. Executed the workflow and saw a deprecation warning. Reviewers: #blessed_reviewers, epriestley Reviewed By: #blessed_reviewers, epriestley Subscribers: epriestley, Korvin, aurelijus Maniphest Tasks: T5655 Differential Revision: https://secure.phabricator.com/D9983		2014-07-22 07:49:15 +10:00
..
engine	Don't explicitly name abstract base classes	2014-07-22 07:49:15 +10:00
renderer	Remove @group annotations	2014-07-09 09:12:13 +10:00
ArcanistUnitTestResult.php	Remove @group annotations	2014-07-09 09:12:13 +10:00