From owner-svn-doc-head@FreeBSD.ORG Sun Mar 22 19:28:20 2015 Return-Path: Delivered-To: svn-doc-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 148A6C56; Sun, 22 Mar 2015 19:28:20 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (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 EA82898E; Sun, 22 Mar 2015 19:28:19 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t2MJSJak067521; Sun, 22 Mar 2015 19:28:19 GMT (envelope-from allanjude@FreeBSD.org) Received: (from allanjude@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t2MJSJ0B067520; Sun, 22 Mar 2015 19:28:19 GMT (envelope-from allanjude@FreeBSD.org) Message-Id: <201503221928.t2MJSJ0B067520@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: allanjude set sender to allanjude@FreeBSD.org using -f From: Allan Jude Date: Sun, 22 Mar 2015 19:28:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46364 - head/en_US.ISO8859-1/articles/problem-reports X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2015 19:28:20 -0000 Author: allanjude Date: Sun Mar 22 19:28:18 2015 New Revision: 46364 URL: https://svnweb.freebsd.org/changeset/doc/46364 Log: Update PR article to ask people not to submit PRs about outdated ports PR: 194721 Differential Revision: https://reviews.freebsd.org/D2092 Submitted by: marino (original) Reviewed by: wblock, Andrew Berg (earlier version) Approved by: bcr (mentor) Sponsored by: ScaleEngine Inc. Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml Modified: head/en_US.ISO8859-1/articles/problem-reports/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/problem-reports/article.xml Sun Mar 22 19:26:11 2015 (r46363) +++ head/en_US.ISO8859-1/articles/problem-reports/article.xml Sun Mar 22 19:28:18 2015 (r46364) @@ -101,30 +101,29 @@ for an answer, consider posing the question to the &a.questions;. - Some cases where it may be appropriate to submit a problem - report about something that is not a bug are: + Consider these factors when submitting PRs about ports or + other software that is not part of &os; itself: - Notification of updates to externally maintained - software (such as ports or software in the contrib/ - directory). + Please do not submit problem reports that simply state + that a newer version of an application is available. Ports + maintainers are automatically notified by + portscout when a new version of + an application becomes available. Actual patches to update + a port to the latest version are welcome. + + For unmaintained ports (MAINTAINER - contains ports@FreeBSD.org), such update - notifications might get picked up by an interested - committer, or you might be asked to provide a patch to - update the port; providing it upfront will greatly improve - your chances that the port will get updated in a timely - manner. - - If the port is maintained, PRs announcing new upstream - releases are usually not very useful since they generate - supplementary work for the committers, and the maintainer - likely knows already there is a new version, they have - probably worked with the developers on it, they are probably - testing to see there is no regression, etc. + is ports@FreeBSD.org), + a PR without an included patch is unlikely to get picked up + by a committer. To become the maintainer of an + unmaintained port, submit a PR with the request (patch + preferred but not required). + + In either case, following the process described in Porter's Handbook will yield the best results. (You might