Date: Sat, 14 Jul 2012 18:24:11 +0300 From: Vitaly Magerya <vmagerya@gmail.com> To: Chris Rees <crees@freebsd.org> Cc: freebsd-ports@freebsd.org, Radim Kolar <hsn@filez.com> Subject: Re: maintainer timeout for FreeBSD commiters Message-ID: <CAL409KzKvGZofXuRhk4q2Y3pYGLwpODoboHOeh_OPKNMNAcJGQ@mail.gmail.com> In-Reply-To: <CADLo83_a=qOqTgGQF%2BLSYyGDaJoT6B2vF9JGV=a2ZHRXRyR6Pw@mail.gmail.com> References: <50017C97.3050200@filez.com> <CADLo83_a=qOqTgGQF%2BLSYyGDaJoT6B2vF9JGV=a2ZHRXRyR6Pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chris Rees <crees@freebsd.org> wrote: > No-one is exempt from timeouts on ports except secteam and portmgr. One problem (at least how it appears to me) is that when a PR gets automatically assigned to a maintainer who is also a committer, it is not automatically unassigned if the person is missing for a few months, and other committers ignore the PR because it is already assigned. This only happened once to me, but it took 6 months for another committer to notice it. And that was pretty fast, comparing to, say ports/154456 [1], which is open since 2011-02. Is automatic unassignment possible? [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/154456
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAL409KzKvGZofXuRhk4q2Y3pYGLwpODoboHOeh_OPKNMNAcJGQ>