Changes between Version 2 and Version 3 of Design/VersionControlSystem


Ignore:
Timestamp:
Oct 21, 2008 3:10:46 AM (6 years ago)
Author:
simonpj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Design/VersionControlSystem

    v2 v3  
    11= GHC Version Control plans = 
    22 
    3  * We plan to move from Darcs to Git for GHC itself.  The recent flurry of work on Darcs is very encouraging, but GHC is a particularly high-end client, and taking a direct dependency leads to stress at both ends. 
     3We plan to move from Darcs to Git for GHC itself.  The recent flurry of work on Darcs is very encouraging, but GHC is a particularly high-end client, and taking a direct dependency leads to stress at both ends.  This page describes the plan.  See [wike:DarcsConversion] for more details about the conversion process, and [wiki:GitForDarcsUsers] for a quick reference on how to use Git. 
    44 
    5  * We do not plan to change before the 6.10 release. Doing so would be destabilising at a time when we are trying to stabilise; and we need to devote all our active cycles to getting 6.10 out.  Yes, that means it'll be more painful to move patches from the (Git) HEAD to the (Darcs) 6.10 branch, but we'll put up with that.  We'll delay the change until the 6.10 branch seems to have settled down; i.e. roughly 6.10.2. 
     5We do not plan to change before the 6.10 release. Doing so would be destabilising at a time when we are trying to stabilise; and we need to devote all our active cycles to getting 6.10 out.  Yes, that means it'll be more painful to move patches from the (Git) HEAD to the (Darcs) 6.10 branch, but we'll put up with that.  We'll delay the change until the 6.10 branch seems to have settled down; i.e. roughly 6.10.2. 
    66 
    7  * A very desirable goal is that it be possible to build GHC with only Git, rather than requiring every developer to actively use both Darcs and Git.  But, many of the libraries are maintained by others (notably Cabal) who, for good reasons, do not want to move. 
     7A very desirable goal is that it be possible to build GHC with only Git, rather than requiring every developer to actively use both Darcs and Git.  But, many of the libraries are maintained by others (notably Cabal) who, for good reasons, do not want to move. 
    88 
    9 In what follows the "Boot Libraries" are the ones required to build GHC. 
     9In what follows the "Boot Libraries" are the ones required to build GHC itself. 
    1010 
    1111We propose the following: