number .travis/ script according to build lifecycle and add README to…

… explain

.travis.yml

@@ -29,13 +29,13 @@ env:
     - WINEDEBUG=fixme-all
     - DOCKER_PACKAGES="build-essential libtool autotools-dev automake pkg-config bsdmainutils curl git ca-certificates ccache"
 before_install:
-  - source .travis/before_install.sh
+  - source .travis/test_03_before_install.sh
 install:
-  - source .travis/install.sh
+  - source .travis/test_04_install.sh
 before_script:
-  - source .travis/before_script.sh
+  - source .travis/test_05_before_script.sh
 script:
-  - source .travis/script.sh
+  - source .travis/test_06_script.sh
 after_script:
   - echo $TRAVIS_COMMIT_RANGE
   - echo $TRAVIS_COMMIT_LOG
@@ -53,7 +53,7 @@ jobs:
       before_script:
         - git fetch --unshallow
       script:
-        - source .travis/lint.sh
+        - source .travis/lint_06_script.sh
 # ARM
     - stage: test
       env: >-

.travis/README.md

@@ -0,0 +1,8 @@
+## travis build scripts
+
+The `.travis` directory contains scripts for each build step in each build stage.
+Currently the travis build defines two stages `lint` and `test`. Each stage has
+it's own [lifecycle](https://docs.travis-ci.com/user/customizing-the-build/#the-build-lifecycle).
+Every script in here is named and numbered according to which stage and lifecycle
+step it belongs to.
+