On 01/19/2015 09:58 PM, Michael Raskin wrote:
Travis is not a good fit to us, as it times out all the time. It's
a pity.
Yes, for large changes it doesn't work because of limits.
hydra.nixos.org is under our administration, so it would be better to
run tests in there, but now it's certainly
On Mon, Jan 19, 2015 at 9:58 PM, Michael Raskin 7c6f4...@mail.ru wrote:
We did already some helpful steps (travis for PRs, staging and release
branches, ...), but we probably need some more.
Travis is not a good fit to us, as it times out all the time. It's
a pity.
I am not sure initial
On 19-01-2015 23:58:19, Michael Raskin wrote:
We did already some helpful steps (travis for PRs, staging and release
branches, ...), but we probably need some more.
Travis is not a good fit to us, as it times out all the time. It's
a pity.
Just let me mention drone[0]!
I started
The problem about being cheap and yet being thought is because basically we
don't have a policy. For example the recent issue about nginx with Restart
and RestartSec. What should be the default Restart for our services?
RestartSec? Should they wait for network or not?
Ecc.
I'd ask everybody about
Hi Michael,
I think we all admit that we have a problem with timely merging of pull
requests.
my impression is that we have a problem with controversial PRs only, because we
lack any kind of organized procedure for making decisions as a group. We merge
PRs that no-one objects to quickly,
