Re: [proto-team] Re: PROTO - proceeding on adding PROTO shepherds to the tracker

Hi Brian,

on 2006-05-16 09:35 Brian E Carpenter said the following:
> Henrik Levkowetz wrote:
...
>> 
>> I think that with no constraint on the amount of change we could
>> introduce I'd advocate a fairly complete set of explicit review
>> actions, and the possibility of setting more than one sub-state
>> at the same time.  Then it's easy for other tools to pick up the
>> sub-state and use that to trigger other actions.  Any free-form
>> field makes that much harder and less predictable; and reducing
>> all the states to very generic ones makes it impossible to kick
>> off a particular review dispatch from the state change.
>> 
>> Whether we have the option to include this in the work package I
>> don't know, however.
> 
> I would hate the result to be that the tracker artificially
> serializes reviews.
> 
> I think that you should include the requirement, but with
> flexibility for the implementor. If handling multiple parallel
> review-waits is a challenge, the fallback as you say is annotation.
> (You already have "5 reviews" as a substate. I was wondering
> how that was going to be handled, except by annotation.)

How about adding this at the end of Section 3.1:

   "In several cases, such as for the 'WG Document Awaiting Reviews'
   state, it is highly desirable to be able to set multiple sub-states
   at the same time (R-013).  This is in order to avoid serialisation of
   reviews because the tracker doesn't support showing and indicating
   parallel reviews."

?

	Henrik

_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team