From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: stability of master - just QA and hydra is not enough Date: Sat, 1 Jul 2017 17:36:04 +0000 Message-ID: <20170701173604.vjzta4fccjfuqxoy@abyayala> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="fyn47ails6ipwrgi" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:59714) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dRMJd-00037S-NE for guix-devel@gnu.org; Sat, 01 Jul 2017 13:36:19 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dRMJa-000142-L4 for guix-devel@gnu.org; Sat, 01 Jul 2017 13:36:17 -0400 Received: from aibo.runbox.com ([91.220.196.211]:45640) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1dRMJa-00012u-EZ for guix-devel@gnu.org; Sat, 01 Jul 2017 13:36:14 -0400 Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1dRMJX-0004cZ-0u for guix-devel@gnu.org; Sat, 01 Jul 2017 19:36:11 +0200 Received: from [163.172.212.115] (helo=localhost) by mailfront12.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1dRMJT-0004Z0-9H for guix-devel@gnu.org; Sat, 01 Jul 2017 19:36:07 +0200 Content-Disposition: inline List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org --fyn47ails6ipwrgi Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable (This is brief and incomplete, just the way I see it right now) Hi, in the recent months (or rather: regulary) guix master is regulary unusable. To be accepted as a system which anyone can use even without the need of having to run from git, the current deployment process (is this called deployment? at least I mean the commit getting into the master branch) isn't really acceptable =66rom a technical and social perspective. I have no formal solution but I want to have this dicussion because I can no longer stand the state of how often "assumed to work" commits are pushed. QA is not enough, and waiting for hydra to pick up on the failure isn't either. We need to revise the way commits land in master. Master can be relatively stable. We should aim for stable with a combination of extending the QA process and a technical approval mechanism. Obviously we can't catch every error, that's what hydra/cuirass[0] is for. What we can and should catch is a set of defined scenarios. =46rom my perspective GuixSD is the primary concern here for me, I don't care for Guix on other systems. In this rather not well though through scenario (give me 2 - 3 weeks and I can write down my whole ideas, I have a busy schedule) I imagine that _before_ commits end up in master we build a set of virtual systems which at least must: - be build successfully - run through the initrd - briefly see the login manager We then need guidelines which commits are classified for building on which set of test machines. Finally the commit must be approved by more than 1 person and commited. There are odds and scenarios we can not test, but what we can test we should test. Stability must not be an enterprise feature (as it was mentioned in the past), it is expected by people who don't want to waste time with developing. Even reporting bugs is only done by those who bother to do so or are able to. I have more to add to the reasons when I can send out an longer email, this is just a bit of an impulse. 0: What is it these days? Is hydra now just a in-retirement frontend for cuirass or how does bayfront work these days? I understand cuirass, not hydra. --=20 ng0 GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588 GnuPG: https://n0is.noblogs.org/my-keys https://www.infotropique.org https://krosos.org --fyn47ails6ipwrgi Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAllX3YQACgkQ4i+bv+40 hYgcKQ/+IRkZof2mPVVk4wQPzBTmZFU9Kx+n3k6RlNvrGCZL5Dh7a7lvSuO+PKxr yxhqPoPNw0FW+/EFurv2frB1Seq81RhXO8Ijybo2QnXyzril0mGaB2yICNB0XOBA olZ+dXjYIhpMtqB/2HPuLXU3rZJxtXbxyB/7kAchKrxQkoa75rLhLHiTq8/M7QD5 OvWIbZt3wF7l2hsHy+jPARCAPUSXox14yUp3RR1VIjfqvIfK92WsK7hzpppbE+Xn gAftr2y1UPb9EAVjYmPLuJ5brayQT1+kzAL50aogIqLVYR9sFGdilL74/ZWBJ6UG yKOtpSOUPW2a67AwmLzjCya2x/+ZCAfcQHVU80DSRz8B1vrQyXtPOv5mZtDuiCuf 7WrSgRmAjoTax+Wp3/ZjURdvwyPb0jBXpAmTMRLLiUf0z3CHAIDlk6FNNcCU2+60 QIqQ7/x+nDC65G7TKplxMERWPSKNK506mGSHnK7SxJjDV+FBRookZYoDObKwsWF9 5Dy2FewkoCUHIcifTX/OZWGS1L1nzYrvO/lOFkWOb5VzCfjfh4p3jILjD9yrlW3S /fUFbmi8pXPSJvs6YJ6jeF8OK1EA0PhnPi69QDj1Uu1BpWPA9ozod4YCXXdMC1xw d0F+6ZIYx4b48K3A5YIdHZQ08H6P/P4r5G6oVT1js0/Z8zcnGbM= =gdMu -----END PGP SIGNATURE----- --fyn47ails6ipwrgi--