From owner-freebsd-ports@FreeBSD.ORG Mon Mar 25 10:21:06 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BF090388 for ; Mon, 25 Mar 2013 10:21:06 +0000 (UTC) (envelope-from vmagerya@gmail.com) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by mx1.freebsd.org (Postfix) with ESMTP id 4CEE0D84 for ; Mon, 25 Mar 2013 10:21:06 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id fs12so10895812lab.39 for ; Mon, 25 Mar 2013 03:21:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=UyStjJKpXIY5b3N4aWV0vpooGjJwxoh1UU/NAI9qU8I=; b=lPH8jka58t4LFdSULUwv6w6SRL8M/Bb4HzO+L1x9k8Mq60dCHZWVRmui/gW25sEVJ3 r7K6MnJvJgTkozz5GSHTN12stWKnFtyGx9d8snTT+N+fH7/nfkBhEjP0nV2JVnQq/VCx 8Xhb47qfY6LInO6yo86Y02cT1nM5mQ+pmCUjsc9v+ga0TPTHd1biHf/lbbFiCc6unPxj dwKzhTuPqLvFhQOpc54KqokVmlA2hWbgAUwNp6qOurhdMptHSr3OkhfsIySnd+5y5JWQ 1uUgGMIjDdfSVOjXLa3OQvXyxBXElnpd4WjCTW5uwr8SVkd6PQQhYR95q2lXeygdxobN 6tBA== X-Received: by 10.112.125.33 with SMTP id mn1mr1835000lbb.89.1364206865198; Mon, 25 Mar 2013 03:21:05 -0700 (PDT) Received: from [172.29.2.131] (altimet-gw.cs2.dp.wnet.ua. [217.20.178.249]) by mx.google.com with ESMTPS id mq7sm4862141lab.1.2013.03.25.03.21.03 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Mar 2013 03:21:04 -0700 (PDT) Message-ID: <515024B0.7020807@gmail.com> Date: Mon, 25 Mar 2013 12:19:28 +0200 From: Vitaly Magerya User-Agent: Thunderbird MIME-Version: 1.0 To: freebsd-ports@freebsd.org Subject: Re: maintainer timeout for FreeBSD commiters References: <50017C97.3050200@filez.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2013 10:21:06 -0000 On 2012-07-14 18:27, Chris Rees wrote: > On 14 July 2012 16:24, Vitaly Magerya wrote: >> 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? > > Technically yes, but it's highly undesirable. You can feel free to > bring it up here if you think that's happened. Hi, everyone. Two of my PRs, ports/175223 [1] and ports/176701 [2], have been automatically assigned to committers, and both have reached maintainer timeout a while ago. Could someone unassign them, so other committers could take a look? Thanks in advance. (I still think this should be done automatically. I would prefer not to bother everyone at ports@ for such things). [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/175223 [2] http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/176701