Date: Fri, 14 Dec 2018 19:11:12 +1100 From: Kubilay Kocak <koobs@FreeBSD.org> To: Arthur Pirika <arfy32@gmail.com> Cc: Lars Engels <lars.engels@0x20.net>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org> Subject: Re: A potential new porter seeking some clarifications Message-ID: <a92e5c2d-c3a9-eac1-ffbd-c0fa3d604982@FreeBSD.org> In-Reply-To: <ada69646-2c40-a928-e078-58dc85a935c8@FreeBSD.org> References: <5c126f7f.1c69fb81.88ea9.6a7a@mx.google.com> <20181213151151.GG37809@e.0x20.net> <ada69646-2c40-a928-e078-58dc85a935c8@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14/12/2018 7:09 pm, Kubilay Kocak wrote: > While special targets (check-plist) can be and are useful, the only form > of QA we should be doing is 'all of it', and at the present moment, that > is: > > 1) portlint -AC (or better) > 2) poudriere testport (supported versions/archs, at least tier1 [1]) > 3) make test for run-time QA [2] I forgot: 4) DEVELOPER=yes in /etc/make.conf for extra sanity checks > > Even (1) and (2) alone, while being the making up the bulk of our QA, > which is notable not 'everything, everytime', is insufficient, as it > mostly picks up only 'our' errors, not the softwares issues, which > ultimately impact users. > > [1] non tier1 is not as trivial as it should be to setup in poudriere. > [2] if test suites exist, TEST_DEPENDS and test: target should be hooked up > > ./koobs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a92e5c2d-c3a9-eac1-ffbd-c0fa3d604982>