Date: Mon, 11 Aug 2014 15:44:38 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 190381] [Patch] Rename and Update of mail/rss2email Ports Message-ID: <bug-190381-13-Cs7jIuOJLy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-190381-13@https.bugs.freebsd.org/bugzilla/> References: <bug-190381-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=190381 John Marino <marino@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |marino@FreeBSD.org --- Comment #6 from John Marino <marino@FreeBSD.org> --- I'm probably going to propose a workflow soon (flow chart) based on my recent experiences. I've been using "patch-ready" to mean "the changes described in the PR (patches, text, what) have been evaluated to some extent, and should reasonably apply and pass all build tests". Basically it's highest status a PR can achieve prior to be committed, so the person setting it is stating they think the PR is ready for committing. This is why I've increasing been insisting on build logs. I give maintainer updates more room, especially if it's a known maintainer with a good reputation and it's not a staging PR. -- 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-190381-13-Cs7jIuOJLy>