Changes between Version 6 and Version 7 of ReviewProcessRevisions


Ignore:
Timestamp:
May 25, 2014, 5:19:48 PM (8 years ago)
Author:
Gordon Woodhull
Comment:

wiki won't let me strikeout in quotations

Legend:

Unmodified
Added
Removed
Modified

  • ReviewProcessRevisions

    v6 v7  
    1515- passing on of orphaned reviews
    1616
    17 Except for the new Boost Library Incubator, there is no attempt to improve the process.  The purpose is to document the process as it exists today.
    18 
    19 > For context, most of the original text of the pages is quoted
     17Except for the new Boost Library Incubator, there is no attempt to improve the process.  The purpose of this page is to document the process as it exists today.
     18
     19> For context, much of the original text of the pages is quoted
    2020
    2121Subjective advice is ''in italics''; part of the proposal is to include this or put it into an 'Advice for Authors and Review Managers' page.
    … …  
    2525http://www.boost.org/community/review_schedule.html
    2626
    27 > Reviews are usually scheduled --on a first-come-first-served basis, and normally last ten days.-- See Formal Review Process for more information.
     27> Reviews are usually scheduled on a first-come-first-served basis, and normally last ten days. See Formal Review Process for more information.
    2828
    2929Reviews are scheduled when the review wizards approve a review manager and agree with the manager and author on dates.  Reviews normally last ten days...
    … …  
    3636== Determine interest
    3737
    38 > Potential library submitters should --use the Boost developers mailing list as a forum-- to gauge interest a possible submission.
     38> Potential library submitters should use the Boost developers mailing list as a forum to gauge interest a possible submission.
    3939
    4040
    … …  
    117117
    118118== Before Requesting a Formal Review
    119 > Read and follow the Boost submission process. There are --at least four steps-- a library author must take before a formal review is requested.
     119> Read and follow the Boost submission process. There are at least four steps a library author must take before a formal review is requested.
    120120
    121121... several steps ...
    … …  
    149149> The Review Manager:
    150150
    151 >       * Checks the submission to make sure it really is complete enough to warrant formal review. --See the Boost Library Requirements and Guidelines--. If necessary, work with the submitter to verify the code compiles and runs correctly on several compilers and platforms.
     151>       * Checks the submission to make sure it really is complete enough to warrant formal review. See the Boost Library Requirements and Guidelines. If necessary, work with the submitter to verify the code compiles and runs correctly on several compilers and platforms.
    152152
    153153See the Boost Library Requirements and Guidelines - or submitting through the Boost Library Incubator will
    … …  
    188188
    189189>       * When a formal review is requested for a library:
    190 >               * --Assign a review manager-- and
     190>               * Assign a review manager and
    191191
    192192* Approve the review manager based on their participation in the Boost community, including the mailing list.  ''and previous reviews?  Stack Overflow participation?''