Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 May 2014 10:20:15 +0200
From:      John Marino <freebsd.contact@marino.st>
To:        Dominic Fandrey <kamikaze@bsdforen.de>, portmgr-feedback@FreeBSD.org,  FreeBSD Ports <ports@FreeBSD.org>
Subject:   Re: ACTION REQUIRED - Unstaged Ports being DEPRECATED on June 31st.
Message-ID:  <5370843F.8070104@marino.st>
In-Reply-To: <53707FF6.3010300@bsdforen.de>
References:  <536E46E0.7030906@FreeBSD.org> <53707FF6.3010300@bsdforen.de>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5370843F.8070104>