[Mpi-22] SVN committing MPI-2.2 latex

Jeff Squyres jsquyres at [hidden]
Fri Jun 12 10:47:48 CDT 2009


Ok, try this diagram.

On Jun 12, 2009, at 5:53 AM, Rolf Rabenseifner wrote:

> Aswers below
>
> On Fri, 12 Jun 2009 05:09:51 -0700
>   Jeff Squyres <jsquyres_at_[hidden]> wrote:
> > On Jun 11, 2009, at 11:20 AM, Rolf Rabenseifner wrote:
> >
> >> In your state diagram, you may differentiate between ticket author
> >> and chapter author.  Please can you use a new color for the  
> chapter-
> >> author trasitions.
> >>
> >
> > Can do.
> >
> >> If a reviewer detects a bug, he should set the state back to
> >> "Passed".  A new color for the reviewer is also needed for this
> >> transition.
> >>
> >
> > I think that this is what I was thinking when I had an extra state
> >in  my first diagram -- that the states would go between "text
> >committed"  and "waiting for PDF reviews" until it was finally
> >"ticket complete".
> >
> > So do you want to make the reviewers responsible for changing the
> > state back away from "waiting for PDF reviews" to the previous
> >state?   That would be different than what we did for proposals,
> >where the  proposal author or chair would move the ticket between
> >"forum feedback  requested", "not ready", and "waiting for (proposal)
> >reviews".
>
> Yes, because we have three parties: The ticket author who has only a
> controling role, the reviewers, and the chapter author.
> It must be absolutely sure, that the chapter author savely detects
> when he has to repair something. Therefore I would like that
> the status goes back to "Passed". This should be done by the reviewer
> as soon as he detects a problem. This reduces the risk, that something
> is overseen.
>
> The ticket author is doing only the final transition to "Ticket
> complete"
> after he and his 4 reviewers have checked the ticket-text in
> the MPI-2.2 standard.
> The ticket author may also be active, if the chapter author
> has not seen that a problem was detected and he has to repair
> something.
>
> Please, can you mention at the forward transition
> from "Passed" to "Waiting for PDF reviews":
>
>     Set by a chapter author when all involved chapter authors
>     have finished the MPI-2.2 latex text and produced a sniplet
>     of pdf pages of this ticket.
>
> Please, can you mention at the backward transition
> from "Waiting for PDF reviews" to "Passed":
>
>     Set back by a reviewer if he detects a bug in the pdf file.
>
> We must be sure, that all 85 tickets are handled correctly
> by the 13 chapter authors.
>
> Rolf
> >
> > --
> > Jeff Squyres
> > Cisco Systems
> >
> > _______________________________________________
> > mpi-22 mailing list
> > mpi-22_at_[hidden]
> > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
>
> Dr. Rolf Rabenseifner . . . . . . . . . .. email rabenseifner_at_[hidden]
> High Performance Computing Center (HLRS) . phone ++49(0)711/685-65530
> University of Stuttgart . . . . . . . . .. fax ++49(0)711 / 685-65832
> Head of Dpmt Parallel Computing . . . www.hlrs.de/people/rabenseifner
> Nobelstr. 19, D-70550 Stuttgart, Germany . (Office: Allmandring 30)
> _______________________________________________
> mpi-22 mailing list
> mpi-22_at_[hidden]
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
>


-- 
Jeff Squyres
Cisco Systems




* 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MPI-2.2_ticket_states.pdf
Type: application/pdf
Size: 467281 bytes
Desc: MPI-2.2_ticket_states.pdf
URL: <http://lists.mpi-forum.org/pipermail/mpi-22/attachments/20090612/6618cb44/attachment.pdf>


More information about the Mpi-22 mailing list