Changes between Version 16 and Version 17 of Development/Patches


Ignore:
Timestamp:
Dec 5, 2012, 12:44:38 PM (7 years ago)
Author:
benl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Development/Patches

    v16 v17  
    1010 * Before sending or pushing patches do the following:
    1111{{{
    12   make cleanLibrary
    13   make cleanWar
     12  make clean
    1413  make war
    1514}}}
    1615
    17  This will clean out the libraries and test directory, rebuild the libraries, then run all the regression tests in the normal (non-optimised) way. This is the ''minimal'' required testing before pushing patches into the head branch. If you've made a deep change to something like the type inferencer or core transforms then you should run all the tests in all possible ways:
     16 This will do a fresh rebuild, then run all the regression tests for the new (non-alpha) compiler. This is the ''minimal'' required testing before pushing patches into the head branch. If you've made a deep change to something like the type inferencer or core transforms then you should run all the tests in all possible ways:
    1817{{{
    19   make cleanLibrary
    20   make cleanWar
    21   make totalwar
     18  make clean
     19  make total
    2220}}}
    2321
    2422 If you've added a lot of files to the version control system (`darcs add`) and might have forgot some, or you just want to be extra sure you're not going to break anything, then it's best to use a separate testing repo. First make a new version of the head repo (maybe called `ddc-head-test`). Record your patches in the original repo, push them into the testing repo, then in that repo do:
    2523{{{
    26   make cleantotal
     24  make clean
     25  make total
    2726}}}
    2827