[Mpi-22] MPI 2.2 Reminders
jsquyres at [hidden]
Fri Dec 5 16:50:04 CST 2008
I sent this diagram of ticket states around shortly after the last
meeting, but I didn't get any comments back. So perhaps it would be
better to send it to a wider audience.
According to this diagram, any ticket in the "Not ready" / "Forum
feedback requested" / "Waiting for reviews" state could be waiting for
reviews. Perhaps we need something better than this (i.e., a separate
bit indicating that a ticket is awaiting reviews).
On Dec 5, 2008, at 11:13 AM, Supalov, Alexander wrote:
> It would be great to learn how to identify tickets that are up for
> review in the first place. All colors and fields I can see in the
> standard reports don't seem to help much in this.
> Best regards.
> -----Original Message-----
> From: mpi-22-bounces_at_[hidden] [mailto:mpi-22-bounces_at_[hidden]
> ] On Behalf Of William Gropp
> Sent: Friday, December 05, 2008 5:07 PM
> To: Bronis R. de Supinski; MPI 2.2
> Subject: Re: [Mpi-22] MPI 2.2 Reminders
> As an immediate step, we can do the following:
> Authors of tickets that are ready for review should do the following:
> (a) add a comment to the ticket with the names of the reviewers (the
> relevant chapter author and 3 other volunteers)
> (b) contact the reviewers to remind them
> Having a separate, searchable field would be nice, but this would
> capture the data now.
> On Dec 5, 2008, at 10:00 AM, Bronis R. de Supinski wrote:
>> Bill and Jeff:
>> It will be really useful if the tickets listed reviewers. In the
>> we need some way to map tickets to reviewers (I am thinking about
>> authors in particular), Could Jeff add a field (or fields) that the
>> owner is responsible for completing that indicates the reviewers?
>> As it is I am really unclear over what I am supposed to review. I am
>> guessing there are at least one or two for my chapter...
>> On Fri, 5 Dec 2008, William Gropp wrote:
>>> Our next MPI 2.2 discussion is in just over a week, and we have a
>>> to do. Please have a look at the wiki for the following (see https://
>>> for the reports):
>>> 1) For your own tickets, make sure that they are up to date. If
>>> reviewers are needed, please contact them and encourage them to
>>> their reviews. If revised text is needed, please update the text
>>> if you would like early feedback, notify this list.
>>> 2) For items on which you are a reviewer (particularly MPI 2.1
>>> authors), please review the relevant tickets. When you are
>>> text, make sure that you are looking at the current MPI 2.1
>>> check page and line numbers as well as the context to ensure that
>>> change is correct.
>>> 3) For other tickets, review them and raise any issues that you have
>>> *now* so that we can start the discussion before our meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 381894 bytes
More information about the Mpi-22