Date: Fri, 04 May 2018 10:31:32 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 227953] www/py-livereload: update to 2.5.2 Message-ID: <bug-227953-21822-m67GGVn18N@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-227953-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-227953-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227953 --- Comment #5 from Kubilay Kocak <koobs@FreeBSD.org> --- (In reply to Kai from comment #4) Absolutely use maintainer-approval, at least when you are the reporter of the change and maintainer of port being changed. It's how we 'explicitly' see a change is approved by its maintainer, and the flag will make the bug show up in the 'Ports: Maintainer Approved' list (look for it in the footer of bugzilla pages) for committers to easily find things 'ready' to work on. If you propose a change (patch/attachment) for a port you're *not* maintainer of, setting maintainer-approval ? <maintainer-email> on the attachment during creation/upload will allow the maintainer to set it to +, reducing the time to approval/resolution for everyone. If you have any more questions about bug tracking/triage/workflow, don't hesitate to ping us on IRC (#freebsd-bugs / freenode). I have a couple of links you might like -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-227953-21822-m67GGVn18N>