On 11/14/2013 12:24 AM, David Kranz wrote:
1. Developer checks in the zeroth version of a scenario test as work in
progress. It contains a description of the test, and possibly work
items. This will "claim" the area of the proposed scenario to avoid
duplication and allow others to comment through gerrit.
2. The developer pushes new versions, removing work in progress if the
code is in working state and a review is desired and/or others will be
contributing to the scenario.
3. When finished, any process-oriented content such as progress tracking
is removed and the test is ready for final review.
+1 , the description will eventually contribute to documenting the scenarios
yet the submitter (step 1) remains in charge of adding to the draft the
reviewers
how about we map at least one volunteer to each service (via the HACKING
file) and ask submitters to add such a person as reviewer of its drafts
when the tests touch the service? this should help avoid tests duplication.
I very much like the idea of using gerrit for this
--
Giulio Fidente
GPG KEY: 08D733BA | IRC: giulivo
_______________________________________________
OpenStack-dev mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
