Date: Sun, 31 Aug 2014 14:21:58 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 193114] [MAINTAINER] devel/p5-Devel-NYTProf: update to 5.06 Message-ID: <bug-193114-13-JdpDmdWkDy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193114-13@https.bugs.freebsd.org/bugzilla/> References: <bug-193114-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193114 --- Comment #6 from John Marino <marino@FreeBSD.org> --- Vladmir, the new documentation is being drafted. I've seen it, but it's not published yet. The old documentation is here: https://www.freebsd.org/doc/en/books/porters-handbook/porting-testing.html It's obsolete, it doesn't talk about "make check-plist", "make stage-qa", etc, all of which the port *must* pass. You might as well make sure it passes, and we might as well have assurance that it passes these basic tests first. That said, it's more necessary for [new port] and [stage] PRs. It's nice to have on update PRs, which this is. That said, committers will take a tested PR over an untested PR every day of the week. There is a lot of competition for committers' eyes (1500 open PRs!) so it's in your interest to have a good, thoroughly tested PR. If you don't want to test it, don't be surprised if the PR is passed over for newer, tested PRs -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193114-13-JdpDmdWkDy>