Description of problem: Admin should be able to mark project as obsolete and hide from view. This should apply at 2 level - - The whole project regardless of the version - Specific project version.
Restriction applies on obsolete project/project iteration: Translation REST access Translation Memory See https://github.com/zanata/zanata/commit/efac31a3e24684241c74126fd95e5b5f5191ecdb
Added REST API restrictions as well as a status field on projects and iterations. They appear on Project/Iteration GET resources. Since obsolete projects are not visible anyway, the only current values that will be seen are 'Current' and 'Retired'. See https://github.com/zanata/zanata/commit/4d57eb79ac88f6e720a83fd77bb793ace7380293 https://github.com/zanata/zanata/commit/b7976ce5d0aa81fb089feabdf74fe7a4e5a82815
Corrected wrong status on Project when fetching from the REST API. See https://github.com/zanata/zanata/commit/6c9f9010a817baf0e6b27f4212d89a81b3bebecf
For Maven client, ADMIN can still push to a retired project. client API version is 1.4.6-SNAPSHOT, but server API version is 1.5-SNAPSHOT
As I said in https://bugzilla.redhat.com/show_bug.cgi?id=755759#c2 for read-only projects, we should enforce in REST API, and also at the Entity level if feasible. In this case, I think we need we're missing some restrictions in TranslationResourcesService.
Please retest with https://github.com/zanata/zanata/commit/3096605f4d2c42db112d157b6ceb917fec562f67 (master branch)
VERIFIED with Zanata version 1.5-SNAPSHOT (20120208-1817)
*** Bug 756923 has been marked as a duplicate of this bug. ***