[Mpi-22] SVN committing MPI-2.2 latex

[Rajeev Thakur]

That would be good as chapter authors can search for which tickets they
need to incorporate.

> -----Original Message-----
> From: mpi-22-bounces_at_[hidden] 
> [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Jeff Squyres
> Sent: Thursday, June 11, 2009 11:58 AM
> To: MPI 2.2
> Subject: Re: [Mpi-22] SVN committing MPI-2.2 latex
> 
> Do you want to add a field to the tickets with chapter author trac ID?
> 
> 
> On Jun 11, 2009, at 9:24 AM, William Gropp wrote:
> 
> > I've put together a spreadsheet, so I know who they are - and I will
> > let them know.
> >
> > Bill
> >
> > On Jun 11, 2009, at 11:21 AM, Rajeev Thakur wrote:
> >
> > > One question is how do chapter authors know which of the 
> 80+ tickets
> > > for
> > > 2.2 apply to their chapter? And some apply to multiple chapters.
> > >
> > > Rajeev
> > >
> > >> -----Original Message-----
> > >> From: mpi-22-bounces_at_[hidden]
> > >> [mailto:mpi-22-bounces_at_[hidden]] On Behalf Of Jeff  
> > Squyres
> > >> Sent: Thursday, June 11, 2009 7:37 AM
> > >> To: MPI 2.2
> > >> Subject: [Mpi-22] SVN committing MPI-2.2 latex
> > >>
> > >> Torsten raised an excellent point in Menlo Park: we need to
> > >> amend our
> > >> 2.2 ticket process to include appropriate checks after a
> > >> proposal has
> > >> passed to ensure that the resulting text is committed 
> properly and
> > >> without errors.
> > >>
> > >> As discussed in Menlo Park, the suggestion is that 
> chapter authors
> > >> commit the text to SVN and then attach a PDF to the ticket to get
> > >> reviewed by the existing ticket reviewers (potentially just a
> > >> few PDF
> > >> pages showing the changes).  Reviewers check that the
> > >> resulting PDF is
> > >> exactly what was passed in the body of the proposal.  
> Once the PDF
> > >> passes review, the ticket can be closed.
> > >>
> > >> --> Rolf/Bill: chapter authors will need guidance on the  
> > appropriate
> > >> Latex markup for signifying changes for MPI-2.2 (e.g., the text-
> > >> coloring magic).
> > >>
> > >> A picture is worth 1,000 words: I have attached a suggested
> > >> diagram of
> > >> Trac ticket state transitions -- the new states are yellow and
> > >> underlined (some old states changed names slightly; those
> > >> changed are
> > >> yellow/underlined as well).
> > >>
> > >> Comments?  (particularly from Bill and chapter authors)
> > >>
> > >> --
> > >> Jeff Squyres
> > >> Cisco Systems
> > >>
> > >
> > > _______________________________________________
> > > mpi-22 mailing list
> > > mpi-22_at_[hidden]
> > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
> >
> > William Gropp
> > Deputy Director for Research
> > Institute for Advanced Computing Applications and Technologies
> > Paul and Cynthia Saylor Professor of Computer Science
> > University of Illinois Urbana-Champaign
> >
> >
> >
> >
> > _______________________________________________
> > mpi-22 mailing list
> > mpi-22_at_[hidden]
> > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
> >
> 
> 
> -- 
> Jeff Squyres
> Cisco Systems
> 
> _______________________________________________
> mpi-22 mailing list
> mpi-22_at_[hidden]
> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-22
>