Re: [proto-team] Re: PROTO - proceeding on adding PROTO shepherds to the tracker
Brian E Carpenter <brc@zurich.ibm.com> Tue, 16 May 2006 10:00 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1FfwLb-0001VV-6B; Tue, 16 May 2006 06:00:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1FfwLa-0001VN-Bn; Tue, 16 May 2006 06:00:10 -0400
Received: from mtagate4.uk.ibm.com ([195.212.29.137])
by ietf-mx.ietf.org with esmtp (Exim 4.43)
id 1FfwLY-0004Ji-Vu; Tue, 16 May 2006 06:00:10 -0400
Received: from d06nrmr1407.portsmouth.uk.ibm.com
(d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185])
by mtagate4.uk.ibm.com (8.13.6/8.13.6) with ESMTP id k4G9xwDL184526;
Tue, 16 May 2006 09:59:58 GMT
Received: from d06av01.portsmouth.uk.ibm.com (d06av01.portsmouth.uk.ibm.com
[9.149.37.212])
by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id
k4GA0sBi132718; Tue, 16 May 2006 11:00:55 +0100
Received: from d06av01.portsmouth.uk.ibm.com (loopback [127.0.0.1])
by d06av01.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id
k4G9xu5d006899; Tue, 16 May 2006 10:59:56 +0100
Received: from sihl.zurich.ibm.com (sihl.zurich.ibm.com [9.4.16.232])
by d06av01.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id
k4G9xuft006877; Tue, 16 May 2006 10:59:56 +0100
Received: from zurich.ibm.com (sig-9-145-250-42.de.ibm.com [9.145.250.42])
by sihl.zurich.ibm.com (AIX4.3/8.9.3p2/8.9.3) with ESMTP id LAA37396;
Tue, 16 May 2006 11:59:55 +0200
Message-ID: <4469A29A.3010109@zurich.ibm.com>
Date: Tue, 16 May 2006 11:59:54 +0200
From: Brian E Carpenter <brc@zurich.ibm.com>
Organization: IBM
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.6) Gecko/20040113
X-Accept-Language: en, fr, de
MIME-Version: 1.0
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [proto-team] Re: PROTO - proceeding on adding PROTO shepherds
to the tracker
References: <E1FdpF4-0007xU-Fk@megatron.ietf.org> <446715D7.7080701@zurich.ibm.com>
<446726DE.8040904@levkowetz.com> <44673AB3.2050002@zurich.ibm.com>
<4467436E.2060400@levkowetz.com>
<A9A5C496-4C40-43F8-86C7-8EC882AF85D9@osafoundation.org>
<4468F2AA.60707@levkowetz.com> <446980AD.7030200@zurich.ibm.com>
<44699905.1090405@levkowetz.com>
In-Reply-To: <44699905.1090405@levkowetz.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc: Aaron Falk <falk@isi.edu>, Lisa Dusseault <lisa@osafoundation.org>,
iesg@ietf.org, proto-team@ietf.org, mankin@psg.com
X-BeenThere: proto-team@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process and Tools Team <proto-team.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>,
<mailto:proto-team-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:proto-team@ietf.org>
List-Help: <mailto:proto-team-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/proto-team>,
<mailto:proto-team-request@ietf.org?subject=subscribe>
Errors-To: proto-team-bounces@ietf.org
> 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."
Works for me.
Brian
_______________________________________________
proto-team mailing list
proto-team@ietf.org
https://www1.ietf.org/mailman/listinfo/proto-team
- [proto-team] PROTO - proceeding on adding PROTO s… Allison Mankin
- Re: [proto-team] PROTO - proceeding on adding PRO… Bill Fenner
- Re: [proto-team] PROTO - proceeding on adding PRO… Henrik Levkowetz
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- [proto-team] Re: PROTO - proceeding on adding PRO… Henrik Levkowetz
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- [proto-team] Re: PROTO - proceeding on adding PRO… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Lisa Dusseault
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Lisa Dusseault
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Bill Fenner
- Re: [proto-team] Re: PROTO - proceeding on adding… Henrik Levkowetz
- Re: [proto-team] Re: PROTO - proceeding on adding… Brian E Carpenter
- Re: [proto-team] Re: PROTO - proceeding on adding… Lisa Dusseault
- Re: [proto-team] Re: PROTO - proceeding on adding… Bill Fenner
- [proto-team] Re: PROTO - proceeding on adding PRO… Lisa Dusseault
- [proto-team] Re: PROTO - proceeding on adding PRO… Henrik Levkowetz