| 1 |
|
|---|
| 2 | How to release a new version of CIVL.
|
|---|
| 3 |
|
|---|
| 4 | 1. Check all tests pass.
|
|---|
| 5 |
|
|---|
| 6 | 2. Edit the fields named "version" and "date" in class
|
|---|
| 7 | edu.udel.cis.vsl.civl.CIVL to use the new version and today's date.
|
|---|
| 8 |
|
|---|
| 9 | 3. Create the tag: to create version 0.2, for example:
|
|---|
| 10 |
|
|---|
| 11 | svn copy svn://vsl.cis.udel.edu/civl/trunk svn://vsl.cis.udel.edu/civl/tags/0.2
|
|---|
| 12 |
|
|---|
| 13 | 4. Create a new config file for autotest: check out
|
|---|
| 14 | svn://vsl.cis.udel.edu/scripts if you have not already,
|
|---|
| 15 | or update it if you already have a local copy. Create
|
|---|
| 16 | a new file config_civl-0.2.sh (for example) based on
|
|---|
| 17 | one of the other config_civl configuration files. There
|
|---|
| 18 | are 3 points that must be changed: (1) BRANCH should
|
|---|
| 19 | be set to 0.2 (for example); this is the name that will
|
|---|
| 20 | be assigned to this branch, (2) REPO needs to be changed
|
|---|
| 21 | to point to the new tagged version, e.g.
|
|---|
| 22 | svn://vsl.cis.udel.edu/civl/tags/0.2, and (3)
|
|---|
| 23 | WORKER_CONFIG needs to be changed to refer to the
|
|---|
| 24 | same configuration file you are creating, i.e.,
|
|---|
| 25 | ${WORKER_SCRIPT_DIR}/config_civl-0.2.sh in this example.
|
|---|
| 26 | Save this file and commit it.
|
|---|
| 27 |
|
|---|
| 28 | 5. Update the scripts on nikolai:
|
|---|
| 29 | ssh tester@nikolai.cis.udel.edu
|
|---|
| 30 | cd repos/scripts/
|
|---|
| 31 | svn update
|
|---|
| 32 |
|
|---|
| 33 | 6. Log on to vsl.cis.udel.edu, eecise_su svn, and edit
|
|---|
| 34 | /home/svn/repositories/civl/hooks/post-commit
|
|---|
| 35 | by changing the second autotest command to refer to the
|
|---|
| 36 | new version configuration file. (You could also add
|
|---|
| 37 | a completely new autotest command; it will work
|
|---|
| 38 | either way.)
|
|---|
| 39 |
|
|---|
| 40 | 7. Update Trac milestones.
|
|---|
