Date: Sat, 14 Jul 2012 23:21:19 +0400 From: Andrey Chernov <ache@FreeBSD.ORG> 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: <20120714192119.GA61563@vniz.net> 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
On Sat, Jul 14, 2012 at 03:51:23PM +0100, Chris Rees wrote: > On 14 July 2012 15:05, Radim Kolar <hsn@filez.com> wrote: > > can be maintainer timeout for port patch submissions implemented for people > > which are FREEBSD commiters? I see no reason why they should be exception > > from standard port processing. If they do not care about their ports, they > > should not have power to obstruct other people work. > > > > I have really long term bad experience with that (usually there are stuck > > for 6+ months). I know that it was discussed, but nothing constructive was > > done. > > > > currently i have in queue just these 2: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/166488 > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/167289 > > No-one is exempt from timeouts on ports except secteam and portmgr. Oh yeah! Holy secteam@ proves to have ~5 years timeout. I watched if it can grows more, but someone recently commits exact the changes I purpose (apparently without their notice) so bigger timeouts are not proved yet. But I think secteam@ have very good potential in timeouts growing and overcome its own achievement some day. -- http://ache.vniz.net/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120714192119.GA61563>