Description of problem:
Only for 'master' branch:
- make the overall regression lightweight.
- Run what netbsd tests run now for CentOS regression (ie, basic and features in tests) - will mostly take just <2hrs.
- Don't run netbsd builds
- Instead add a compilation test on centos 32bit machine to keep reminding ourself how many warnings we get. (And compilation failure there is -1).
On release-x.y branch:
- Continue with the currently existing voting rights, and the tests would be different. (ie, full regression instead of lightweight regression tests).
More info on this is found @ http://lists.gluster.org/pipermail/maintainers/2017-May/002587.html
1) I'm thinking we just run the tests/basic folder?
2) Do you mean netbsd builds or regressions? The netbsd build (netbsd6-smoke) itself takes a short duration and is trivial to run. I recommend we keep that remove the NetBSD voting job. Additionally, are we running the netbsd regressions on a nightly basis now?
3) We already have a 32-bit compilation test in the form of strfmt_errors. Do we want more?
On release branch:
As far as I can see, this seems to be "keep going as we do right now". Are we removing netbsd voting regressions here too?
1) tests/basic is good.
2) lets run netbsd6-smoke
3) We can run 'netbsd' job in nightly IMO. (doesn't matter much on 'master' branch decision now).
* For now, lets keep going as is, and see if any changes required later.
All the changes have been made today.