|
1 | | -1) test the current source (standard tests) |
2 | | -> cd ..../adda/src |
3 | | -> make -s |
4 | | -> cd ../tests/2exec |
5 | | -edit comp2exec to compare against previous version |
6 | | -> sh comp2exec seq, mpi, ocl + mpi_seq, ocl_seq |
7 | | - |
8 | | -# extra surface tests (optional, causes a number of false positives) |
9 | | -edit comp2exec to enable SURF_EXT |
10 | | -> sh comp2exec seq, mpi, ocl |
11 | | -edit comp2exec to enable SURF_STANDARD (instead of SURF_EXT) and to compare against adda, etc. in the test directory (.) |
12 | | -> cp ../../src/seq/adda . |
13 | | -> cp ../../src/mpi/adda_mpi . |
14 | | -> cp ../../src/ocl/adda_ocl . |
15 | | -> sh comp2exec seq, mpi, ocl |
16 | | - |
17 | | -# sparse tests (first two lines are not required if done above) |
18 | | -#> cp ../../src/seq/adda . |
19 | | -#> cp ../../src/mpi/adda_mpi . |
20 | | -> cd ../../src |
21 | | -> make seq OPTIONS=SPARSE -s |
22 | | -> cd ../tests/2exec |
23 | | -edit comp2exec to enable SPARSE |
24 | | -> sh comp2exec seq, mpi |
25 | | -edit comp2exec to compare against adda and adda_mpi + enable SPARSE_STANDARD |
26 | | -> sh comp2exec seq, mpi |
27 | | - |
28 | | -2) make sure that manual.doc/pdf, history, and const.h are up to date. In particular, version number in const.h should |
29 | | -not contain "a" or "b" (if not explicitly making beta release). |
30 | | - |
31 | | -3) Update CodeDesign and corresponding schemes in doc/gv/ |
32 | | - |
33 | | -(on 64-bit Windows) |
34 | | -4) sh win_all.sh #.# |
35 | | - |
36 | | -(on Linux) |
37 | | -5) ./zip_packages #.# |
38 | | - |
39 | | -6) Upload packages to GoogleCode |
40 | | -7) Update Wiki pages: PackageDescription, ReleaseNotes, Features |
41 | | -8) Send announcement to users. |
| 1 | +Use some normal shell, under Windows - this can be MSYS. Then 'sh' can be omitted in the following commands. |
| 2 | + |
| 3 | +1) Test for compiler warnings (about 10 min) |
| 4 | +> sh build_debug 2> log_debug |
| 5 | + |
| 6 | +2) Build and test the current source (a few hours) |
| 7 | +> sh test_new 2> log_test |
| 8 | +Before running the tests, make sure that ../tests/2exec/comp2exec script is properly set up. This includes |
| 9 | +the REFPATH (when comparing against previous version) and GUIDIFF. If the latter is used, you generally do |
| 10 | +not need to redirect stdout. |
| 11 | +It is also possible to separately run build and ../tests/2exec/test_all scripts (see help inside them) |
| 12 | + |
| 13 | +3) If any changes are made to the code or tests, commit them now. |
| 14 | + It is also a good idea to repeat some of the above on different systems. |
| 15 | + |
| 16 | +4) make sure that manual.doc/pdf, history, and const.h are up to date. See also versions.txt |
| 17 | +- version number in const.h should not contain "alpha" or "beta" (if not explicitly making beta release). |
| 18 | +- history should contain version date of the in-progress release. |
| 19 | +- manual should have correct version (including links on the first page). Look through the whole manual |
| 20 | + (for figure placement, etc.). Update sample outputs in appendices, if needed. |
| 21 | +- use doiLink macro in Word and produce pdf (better with Actobat plugin - leads to twice smaller size). |
| 22 | + Look through the pdf once more. |
| 23 | + |
| 24 | +5) Update CodeDesign and corresponding schemes in doc/gv/ |
| 25 | + |
| 26 | +6) Make sure that the DLLs in win64/ correspond to the latest executables (to be copied there). They can be |
| 27 | + staged for commit (including deleted older ones) - then they will be committed together with executables. |
| 28 | + |
| 29 | +7) Run the following aggregate script (on Windows), inserting appropriate version number: |
| 30 | +> sh win_all.sh #.#.# |
| 31 | +You can also go through it line by line. |
| 32 | + |
| 33 | +8) It is a good idea to test that the resulting executables can be run with given DLLs. For example you can run |
| 34 | +'set PATH=""' or 'export PATH=""' in a terminal before running the executables (to make other DLLs on your system |
| 35 | +unavailable). |
| 36 | + |
| 37 | +9) Now you are ready to go live (check your commits): |
| 38 | +> git push --tags |
| 39 | + |
| 40 | +10) Prepare binary and source packages |
| 41 | +> zip_packages #.#.# |
| 42 | + |
| 43 | +11) Create release at GitHub using this tag (Release notes is a shortened version of history). Attach the above |
| 44 | +packages to it. |
| 45 | + |
| 46 | +12) Update wiki page Features |
| 47 | + |
| 48 | +13) Send announcement to users. |
| 49 | + |
| 50 | +14) With the next commit update ignore patterns in tests/2exec/comp2exec and, possibly, testing suites to compare |
| 51 | +against the latest release |
0 commit comments