From owner-freebsd-ports@FreeBSD.ORG Mon May 12 08:20:47 2014 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D295582D; Mon, 12 May 2014 08:20:47 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AB7D527F2; Mon, 12 May 2014 08:20:47 +0000 (UTC) Received: from [192.168.0.20] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id 4717D438BD; Mon, 12 May 2014 03:20:31 -0500 (CDT) Message-ID: <5370843F.8070104@marino.st> Date: Mon, 12 May 2014 10:20:15 +0200 From: John Marino Reply-To: marino@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Dominic Fandrey , portmgr-feedback@FreeBSD.org, FreeBSD Ports Subject: Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st. References: <536E46E0.7030906@FreeBSD.org> <53707FF6.3010300@bsdforen.de> In-Reply-To: <53707FF6.3010300@bsdforen.de> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 May 2014 08:20:47 -0000 On 5/12/2014 10:01, Dominic Fandrey wrote: > On 10/05/2014 17:33, Bryan Drewery wrote: >> You are receiving this mail as it affects FreeBSD ports that you maintain. >> >> In September 2013, the Ports framework learned how to Stage ports. >> >> On June 31st, all unstaged ports will be marked DEPRECATED and have >> their MAINTAINER reset. >> On August 31st, all unstaged ports will be removed from the ports tree. > > That's hardly fair with maintainer-updates not being committed for months. I would have thought it to be obvious, but ports with valid and applicable PRs are excluded. No unstaged port with a pending PR to stage it is going to be removed, the PR will get processed instead. > I usually stop updating my ports when that happens and resume my > activity when my confidence that stuff has a chance of being committed > is restored. I.e. when all my old updates have been committed. I commit PR patches that are 6 to 18 months old fairly frequently. There is obviously a huge backlog but many PRs are processed daily. The PRs that aren't getting processed quickly are "[NEW PORT]" PRs (and apparently anything mentioning fuse-fs for some reason). A staging PR is going to jump the line; it has a higher priority. Why would you even entertain the idea that a staging PR will fall between the cracks? John