El 18/08/2014 a las #4, Jörn Friedrich Dreyer escribió:
On 18.08.2014 09:40, David A. Velasco wrote:
My 2 cents.
[...]
The attentive reader will have observed that I got rid of the '6 -
Reviewing' label because assigning that only prevent others from doing a
review. I added a 'Done Done' label though to make explicit that the
code is available to end users.
I don't like this. I understand the problem you point, but if there is a
real interest in
doing some more formalized QA, "hiding" the review step in the process
seems
counterproductive.
There is still the '5 - To review' step. I removed '6 - Reviewing' since
duplicating a review only adds to our quality. And we already want two
:+1:, that cannot really be modeled with a single label. There is no
need to use a 'Reviewing' label to tell make transparent that someone is
currently reviewing, in contrast to the '3 - To develop' / '4 -
Developing' pair.
Hope this clarifies the drop.
Yes, it's clear.
The problem I see is that nobody "assigns himself to take care of the
issue" testing, as occurs between 'To develop' and 'Developing'. That
should be about granting it is tested, not necessarily about testing it
in solitude.
But I understand the difference is in the process, not in the tagging.
_______________________________________________
Devel mailing list
[email protected]
http://mailman.owncloud.org/mailman/listinfo/devel
