Date: Wed, 18 Jul 2018 18:53:37 +0000 From: bugzilla-noreply@freebsd.org To: doc@FreeBSD.org Subject: [Bug 229859] Changes to 5.5 submitter/maintainer/committer approval for port submissions/updates Message-ID: <bug-229859-9-V925eVle4p@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229859-9@https.bugs.freebsd.org/bugzilla/> References: <bug-229859-9@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=3D229859 --- Comment #5 from Kurt Jaeger <pi@FreeBSD.org> --- (In reply to Mathieu Arnold from comment #3) Yes, this can happen. I hope and guess that this would not be the 'new norm= al'. Is there an easy way to detect this case ? In which cases would it be 'very-bad', in which cases would it be 'unfortunate' ? How many times would the maintainer 'not care' ? Do I understand you correctly that you suspect that it would undermine the role of the maintainer, so that in the long run being a maintainer would not be seen as a useful role ? On the other hand, do we really have the problem that we move too fast ? To be honest, some DEPRECATE and EXPIRE runs in the past ran into oppositio= n... --=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-229859-9-V925eVle4p>