Document what to do if an outdated port

is noticed.

PR:		docs/80681
Submitted by:	Roman Neuhauser <neuhauser@sigpipe.cz>
		Ion-Mihai Tetcu <itetcu@people.tecnik93.com>
Approved by:	trhodes (mentor)

en_US.ISO8859-1/articles/problem-reports/article.sgml

@@ -107,6 +107,23 @@
 	  software (mainly ports, but also externally maintained base
 	  system components such as BIND or various GNU
 	  utilities).</para>
+
+	<para>For unmaintained ports (<makevar>MAINTAINER</makevar> contains
+	  <literal>ports@FreeBSD.org</literal>), 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.</para>
+    
+	<para>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.</para>
+    
+	<para>In either case, following the process described in <ulink
+	  url="&url.books.porters-handbook;/port-upgrading.html">Porter's
+	  Handbook</ulink> will yield the best results.</para>
       </listitem>
     </itemizedlist>