Date: Mon, 07 Jun 2021 16:57:07 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 256452] [new port] net-mgmt/unbound-telemetry - replacement for net-mgmt/unbound_exporter Message-ID: <bug-256452-7788-fSgetkFC8v@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-256452-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-256452-7788@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=3D256452 --- Comment #6 from Chris Hutchinson <portmaster@bsdforge.com> --- Points of interest to help accelerate your port through the acceptance process: - Provide QA (Quality Assurnce) provide proof that your port/changes actually work. ports-mgmt/poudriere is the defacto choice for providing the output to prove everything works as intended. Other forms can include relevant output from build logs. from within a jail(8), all of: make -DBATCH check-plist, make stage-qa, make check-sanity, portlint. To name a few. But as a rule, the output of ports-mgmt/poudriere is the preferred proof. - Future maintence of your new port will require you to become well familiar with git(1) if your not already familiar. Even if you are. You'll still need to discover how to use it with regards to maintaining ports, and properly submitting patches. - Become informed. You're also going to want to join at least the freebsd-ports@ and the freebsd-ports-bugs@ mailing lists. It may well be a good idea to also join the dev-commits-ports-all@. As you're going to need to know if things ever "go south" with any of the ports you maintain. All of this is in the porters handbook that I mentioned earlier. But these are some of the main points that will help you "get up to speed". --Chris --=20 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-256452-7788-fSgetkFC8v>