@erco77 Greg, I'll review the changes when time permits (within the next 2 days or so), I'm pretty busy with other things ATM.

Regarding Travis-CI (hint): you can build your branches in your own fork with Travis-CI (I'm doing this, BTW). I don't know if I recall everything correctly but I believe the "only thing you need to do" ;-) is to register with Travis-CI.com (don't use travis-ci.org, this is going to be closed). You can sign-up with your GitHub account which is straight-forward (IIRC you need to grant travis-ci access to your github account to do its job).

Once this is done, every commit you do in one of your branches with names listed in our .travis-ci.yml file will be built automatically and you can view the result. .travis-ci.yml contains these valid branch names:

branches:
  only:
  - master
  - branch-1.3
  - /^feature-.*/
  - /^fix-.*/
  - /^issue-.*/
  - /^str-.*/

Note that all issue-* branches are included, but the '-' is required. You could also change .travis-ci.yml in your branch but I don't recommend this because it would complicate the merge process later (you'd have to reset it at least).

Please let me know if this works for you or not (if you try it at all).

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.