Changes between Version 4 and Version 5 of MoveToModularizedGit


Ignore:
Timestamp:
Oct 10, 2012, 2:17:33 PM (10 years ago)
Author:
Beman Dawes
Comment:

Apply Dave's feedback, plus decomposition

Legend:

Unmodified
Added
Removed
Modified

  • MoveToModularizedGit

    v4 v5  
    33This page is about managing the process of moving Boost version control from Subversion to Git, and in doing so move from a centralized structure to a distributed, modular structure.
    44
    5 == Action Plan ==
     5== Master Action Plan ==
    66
    77||= '''✔''' =||= '''Action''' =||= '''Manager''' =||= '''Due''' =||
    88|| ✔ || Preliminary Steering Committee approval || S/C || May, 2012 ||
    9 || ✔ || Subversion to Git repo move scrips ready || Daniel Pfeifer || ||
    10 || || Web site branch: Subversion references and procedures Gitized || || ||
    11 || || Trac Wiki Subversion references and procedures Gitized || || ||
     9|| 95% || Subversion to Git repo move scrips ready || Daniel Pfeifer || ||
     10|| || Documentation Action Plan (see below) || || ||
    1211|| || Regression test scripts, procedures ready || Test & build teams || ||
    1312|| || Inspect and Release scripts, procedures ready || Release mgrs || ||
    14 || || Modularized Boost 'Help Desk' ready || || ||
    15 || || User accounts and permissions in place || || ||
    16 || || || || ||
    17 || || || || ||
     13|| || Modularized Boost 'Help Desk' || Beman || ||
    1814|| || Final Steering Committee approval || S/C || Prep complete ||
    1915|| || Make Subversion trunk read-only || || ||
    … …  
    2218|| || Web site changes go live || || ||
    2319|| || 'Help Desk' goes live || || ||
    24 || || Open GitHub repos for developer use || || ||
    25 || || || || ||
     20|| || Open !GitHub repos for developer use || || ||
    2621|| || || || ||
    2722
    2823Each time an action item is checked as completed, a brief progress report message should be posted on the developers and users mailing lists. If the milestone is particularly newsworthy, a notice should also be posted on the announce mailing list.
    29  
     24
     25== Documentation Action Plan ==
     26
     27||= '''✔''' =||= '''Action''' =||= '''Manager''' =||= '''Due''' =||
     28|| || Web site branch: Instructions, etc, that mention Subversion changed to use Git || || ||
     29|| || Trac Wiki: Instructions, etc, that mention Subversion changed to use Git || || ||
     30|| || Develop, document, modularization big picture || || ||
     31|| || Develop, document, suggested developer workflows based on Gitflow || || ||
     32|| || Develop, document, how per library !GitHub projects will work, including how permissions work || || ||
     33
     34Any newly developed documentation must be integrated with the current documentation.