OpenSuseBuild service builds and Travis builds can be organized using Github hooks.
This would produce a new version of the master for Linux and OSX.
FreeBSD, OpenBSD would remain manual builds (there is no automatized build system I know
of, which would support those two platforms).
Travis has a cancel-build-feature: if a new master is built and the current builds are aborted
if there is a new check-in on Github.
OBS has this feature since ever.
So we don't have to worry to use too many resources on those build systems.
The current way of manually building OBS versions leads to tedious repetitive work or/and
non-current packages.
Also the Travis CI and OBS builds run on my personal accounts, which makes them most
likely invisible to users.
OpenSuseBuild service builds and Travis builds can be organized using Github hooks.
This would produce a new version of the master for Linux and OSX.
FreeBSD, OpenBSD would remain manual builds (there is no automatized build system I know
of, which would support those two platforms).
Travis has a cancel-build-feature: if a new master is built and the current builds are aborted
if there is a new check-in on Github.
OBS has this feature since ever.
So we don't have to worry to use too many resources on those build systems.
The current way of manually building OBS versions leads to tedious repetitive work or/and
non-current packages.
Also the Travis CI and OBS builds run on my personal accounts, which makes them most
likely invisible to users.