From owner-freebsd-ports@freebsd.org  Sun Aug  9 11:30:50 2015
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DAE4998B9A
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Sun,  9 Aug 2015 11:30:50 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5E1DBD11;
 Sun,  9 Aug 2015 11:30:50 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.86 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1ZOOoU-000C0g-FU; Sun, 09 Aug 2015 13:30:50 +0200
Date: Sun, 9 Aug 2015 13:30:50 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Anders Jensen-Waud <anders@jensenwaud.com>, freebsd-ports@freebsd.org
Subject: Re: lang/mono: Update to 4.0.3.19
Message-ID: <20150809113050.GH40589@home.opsec.eu>
References: <55C7196A.8000600@jensenwaud.com>
 <20150809112030.GG40589@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150809112030.GG40589@home.opsec.eu>
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Aug 2015 11:30:50 -0000

Hi!

> Ok, got that. As Romain is the maintainer of the port, he needs
> to approve PR 201883

Technically, after 14 days oe non-action on a PR, the maintainer is
seen as timed-out for that PR and anyone can commit. This is almost
the case with that PR.

There are other issues to consider:

1) If the port to be updated is a dependency for other ports,
the submitter should probably test if the dependent ports still
build and run with that change and say so in the PR, eg.
"I tested the build of the dependent ports and if they work, see
list attached".

Otherwise the committer has to find the dependent ports, and this
takes time.

I used

grep -Rl '{PORTSDIR}/lang/mono' * > /tmp/mono

on my /usr/ports/ and did not find any port that depends on mono.
This is surprising 8-}

2) If it's an update, provide a changelog entry in the PR.
What happened between the old and the suggested version ?

Otherwise the committer has to find a changelog and this takes time.

-- 
pi@opsec.eu            +49 171 3101372                         5 years to go !