Attachment #175238 for bug #213056

Lines 37-44 Link Here

(-)htdocs/portmgr/charter.xml (-2 / +2 lines)
37	</li>	37	</li>
38		38
39	<li>	39	<li>
40	<p>Maintain the automated <a href="http://pkg.FreeBSD.org">	40	<p>Maintain the automated
41	package building cluster</a>, and make the resulting packages	41	package building cluster, and make the resulting packages
42	available for download by FreeBSD users.</p>	42	available for download by FreeBSD users.</p>
43	</li>	43	</li>
44		44





<p>portmgr also runs periodic builds of proposed large changes to the
  Ports Collection on a dedicated area of the automated
  ports building cluster.  These are termed experimental builds
  (often referred to as "exp-runs").
  Examples of changes that should be tested here before committing
  include:</p>


	ports Makefiles, such as definitions or usage of common make
        variables (or <tt>Makevar</tt>s). (e.g. consolidation of
	various implementations of USE_*, WITH_*, and so forth)</p></li>
  <li><p>large changes to the repository (such as when an existing port category
	is divided up)</p></li>
</ul>

<p>Any large-scale
  failures that might be caused by any of the above need to be caught
  first before a large number of user installations are affected.</p>


  of inter-committer disputes that can not be solved among the
  committers themselves.</p>

<h3>Maintain The Automated Ports Building Cluster</h3>
  Ports Building Cluster</a></h3>

<p>portmgr maintains a set of machines that automatically build
  packages on combinations of FreeBSD source tree versus CPU

Lines 26-32 Link Here

(-)htdocs/portmgr/policies_contributors.xml (-3 / +2 lines)
26		26
27	<p>We have an add-on to the Problem Reports database known as the auto-assigner,	27	<p>We have an add-on to the Problem Reports database known as the auto-assigner,
28	which attempts to automatically notify maintainers of PRs; however,	28	which attempts to automatically notify maintainers of PRs; however,
29	it depends on the Synopsis containing category/portname. In general,	29	it depends on the Summary containing category/portname. In general,
30	various people attempt to catch and fix cases where it does not work,	30	various people attempt to catch and fix cases where it does not work,
31	but you should not assume so. Therefore, please	31	but you should not assume so. Therefore, please
32	check to see whether or not the maintainer knows about the PR before	32	check to see whether or not the maintainer knows about the PR before
Lines 43-50 Link Here
43		43
44	<p>This period may be shortened by portmgr if the email address returns	44	<p>This period may be shortened by portmgr if the email address returns
45	with a hard bounce. In this case, it is probably desirable to reset	45	with a hard bounce. In this case, it is probably desirable to reset
46	all the maintainer's ports and change any PRs set to 'feedback' back	46	all the maintainer's ports and check the status of any PRs.</p>
47	to 'open'.</p>
48		47
49	<a name="commit_privileges"></a>	48	<a name="commit_privileges"></a>
50	<h3>Commit Privileges</h3>	49	<h3>Commit Privileges</h3>




    <body class="navinclude.about">

<p>Support of FreeBSD releases by ports and the ports infrastructure
  currently matches the <a href="&base;/security/#sup">policies
  set out by the FreeBSD Security Officer</a>.  Once a major branch X
  reaches its EOL date, the "last known good" ports tree will be tagged
  with the <tt>RELEASE_X_EOL</tt> tag as a convenience to those

  remaining users who intend to self-support their installations.
  This tag is not supported in any way and security fixes will not be
  applied.  Usage is therefore highly discouraged and should only be
  used if there is no other option; consumers are expected to provide
  their own support.</p>

<p>For all supported major src branches, all ports will be included in
  an automated quality assurance procedure which will build, install,

  href="&base;/doc/en_US.ISO8859-1/articles/committers-guide/archs.html#AEN1259">
  Tier 1 platforms</a>.  Maintainers and committers are notified of
  failures detected during testing.  Ports that are known not to build
  or run on a given supported branch and/or platform will be marked as
  such.</p>

<p>Prebuilt binary packages will also be provided for all major branches

    <th>Estimated EoL</th>
  </tr>
  <tr>
    <td>RELENG_8</td>
    <td>n/a</td>
    <td>RELENG_8_3</td>
    <td>packages-8-stable</td>
    <td>last release + 2 years</td>
   </tr>
   <tr>
     <td>RELENG_8_4</td>
     <td>8.4-RELEASE</td>
     <td>RELENG_8_4</td>
     <td>packages-8-stable</td>
     <td>June 30, 2015</td>
   </tr>
    <tr>
    <td>RELENG_9</td>
    <td>n/a</td>
    <td>RELENG_9_3</td>
    <td>packages-9-stable</td>
    <td>last release + 2 years</td>
  </tr>
  <tr>
     <td>RELENG_9_3</td>
     <td>9.3-RELEASE</td>
     <td>RELENG_9_3</td>
     <td>packages-9-stable</td>
     <td>December 31, 2016</td>
  </tr>
  <tr>
    <td>RELENG_10</td>
    <td>n/a</td>
    <td>RELENG_10_1</td>
    <td>packages-10-stable</td>
    <td>last release + 2 years</td>
  </tr>
  <tr>
     <td>RELENG_10_1</td>
     <td>10.1-RELEASE</td>
     <td>RELENG_10_1</td>
     <td>packages-10-stable</td>
     <td>December 31, 2016</td>
  </tr>
  <tr>
     <td>RELENG_10_2</td>
     <td>10.2-RELEASE</td>
     <td>RELENG_10_1</td>
     <td>packages-10-stable</td>
     <td>December 31, 2016</td>
  </tr>
  <tr>
     <td>RELENG_10_3</td>
     <td>10.3-RELEASE</td>
     <td>RELENG_10_1</td>
     <td>packages-10-stable</td>
     <td>April 30, 2018</td>
  </tr>
  <tr>
    <td>RELENG_11</td>
    <td>n/a</td>
    <td>RELENG_11_1</td>
    <td>packages-11-stable</td>
    <td>last release + 2 years</td>
  </tr>
  <tr>
     <td>HEAD</td>
     <td>n/a</td>
     <td>HEAD</td>
     <td>packages-12-current</td>
     <td>Best Effort</td>
  </tr>
 </table>

<p>Older releases are not maintained; ports and packages may not be able
  to install or run.  Users are strongly encouraged to upgrade to one of
  the supported releases mentioned above.</p>


Lines 41-46 Link Here

(-)htdocs/security/security.xml (+1 lines)
41	<ul>	41	<ul>
42	<li><a href="#recent">Recent FreeBSD security vulnerabilities</a></li>	42	<li><a href="#recent">Recent FreeBSD security vulnerabilities</a></li>
43	<li><a href="#how">How to update your system</a></li>	43	<li><a href="#how">How to update your system</a></li>
		44	<li><a href="#sup">Supported FreeBSD releases</a></li>
44	</ul>	45	</ul>
45		46
46	<a name="recent"></a>	47	<a name="recent"></a>

Return to bug 213056

Lines 31-37 Link Here

(-)htdocs/portmgr/policies.xml (-5 / +5 lines)
31		31
32	<p>portmgr also runs periodic builds of proposed large changes to the	32	<p>portmgr also runs periodic builds of proposed large changes to the
33	Ports Collection on a dedicated area of the automated	33	Ports Collection on a dedicated area of the automated
34	<a href="http://pointyhat.FreeBSD.org">ports building cluster</a>.	34	ports building cluster. These are termed experimental builds
		35	(often referred to as "exp-runs").
35	Examples of changes that should be tested here before committing	36	Examples of changes that should be tested here before committing
36	include:</p>	37	include:</p>
37		38
Lines 43-53 Link Here
43	ports Makefiles, such as definitions or usage of common make	44	ports Makefiles, such as definitions or usage of common make
44	variables (or <tt>Makevar</tt>s). (e.g. consolidation of	45	variables (or <tt>Makevar</tt>s). (e.g. consolidation of
45	various implementations of USE_, WITH_, and so forth)</p></li>	46	various implementations of USE_, WITH_, and so forth)</p></li>
46	<li><p>large repocopies (such as when an existing port category	47	<li><p>large changes to the repository (such as when an existing port category
47	is divided up)</p></li>	48	is divided up)</p></li>
48	</ul>	49	</ul>
49		50
50	<p>Again, since the ports tree is not branched, any large-scale	51	<p>Any large-scale
51	failures that might be caused by any of the above need to be caught	52	failures that might be caused by any of the above need to be caught
52	first before a large number of user installations are affected.</p>	53	first before a large number of user installations are affected.</p>
53		54
Lines 62-69 Link Here
62	of inter-committer disputes that can not be solved among the	63	of inter-committer disputes that can not be solved among the
63	committers themselves.</p>	64	committers themselves.</p>
64		65
65	<h3>Maintain The Automated <a href="http://pointyhat.FreeBSD.org">	66	<h3>Maintain The Automated Ports Building Cluster</h3>
66	Ports Building Cluster</a></h3>
67		67
68	<p>portmgr maintains a set of machines that automatically build	68	<p>portmgr maintains a set of machines that automatically build
69	packages on combinations of FreeBSD source tree versus CPU	69	packages on combinations of FreeBSD source tree versus CPU

Lines 14-20 Link Here

(-)htdocs/portmgr/policies_eol.xml (-29 / +51 lines)
14	<body class="navinclude.about">	14	<body class="navinclude.about">
15		15
16	<p>Support of FreeBSD releases by ports and the ports infrastructure	16	<p>Support of FreeBSD releases by ports and the ports infrastructure
17	matches the <a href="&base;/security/#sup">policies	17	currently matches the <a href="&base;/security/#sup">policies
18	set out by the FreeBSD Security Officer</a>. Once a major branch X	18	set out by the FreeBSD Security Officer</a>. Once a major branch X
19	reaches its EOL date, the "last known good" ports tree will be tagged	19	reaches its EOL date, the "last known good" ports tree will be tagged
20	with the <tt>RELEASE_X_EOL</tt> tag as a convenience to those	20	with the <tt>RELEASE_X_EOL</tt> tag as a convenience to those
Lines 21-27 Link Here
21	remaining users who intend to self-support their installations.	21	remaining users who intend to self-support their installations.
22	This tag is not supported in any way and security fixes will not be	22	This tag is not supported in any way and security fixes will not be
23	applied. Usage is therefore highly discouraged and should only be	23	applied. Usage is therefore highly discouraged and should only be
24	used as a last resort.</p>	24	used if there is no other option; consumers are expected to provide
		25	their own support.</p>
25		26
26	<p>For all supported major src branches, all ports will be included in	27	<p>For all supported major src branches, all ports will be included in
27	an automated quality assurance procedure which will build, install,	28	an automated quality assurance procedure which will build, install,
Lines 29-35 Link Here
29	href="&base;/doc/en_US.ISO8859-1/articles/committers-guide/archs.html#AEN1259">	30	href="&base;/doc/en_US.ISO8859-1/articles/committers-guide/archs.html#AEN1259">
30	Tier 1 platforms</a>. Maintainers and committers are notified of	31	Tier 1 platforms</a>. Maintainers and committers are notified of
31	failures detected during testing. Ports that are known not to build	32	failures detected during testing. Ports that are known not to build
32	or run on a given supported branch or platform will be marked as	33	or run on a given supported branch and/or platform will be marked as
33	such.</p>	34	such.</p>
34		35
35	<p>Prebuilt binary packages will also be provided for all major branches	36	<p>Prebuilt binary packages will also be provided for all major branches
Lines 56-98 Link Here
56	<th>Estimated EoL</th>	57	<th>Estimated EoL</th>
57	</tr>	58	</tr>
58	<tr>	59	<tr>
59	<td>RELENG_8</td>
60	<td>n/a</td>
61	<td>RELENG_8_3</td>
62	<td>packages-8-stable</td>
63	<td>last release + 2 years</td>
64	</tr>
65	<tr>
66	<td>RELENG_8_4</td>
67	<td>8.4-RELEASE</td>
68	<td>RELENG_8_4</td>
69	<td>packages-8-stable</td>
70	<td>June 30, 2015</td>
71	</tr>
72	<tr>
73	<td>RELENG_9</td>	60	<td>RELENG_9</td>
74	<td>n/a</td>	61	<td>n/a</td>
75	<td>RELENG_9_1</td>	62	<td>RELENG_9_3</td>
76	<td>packages-9-stable</td>	63	<td>packages-9-stable</td>
77	<td>last release + 2 years</td>	64	<td>last release + 2 years</td>
78	</tr>	65	</tr>
79	<tr>	66	<tr>
80	<td>RELENG_9_1</td>	67	<td>RELENG_9_3</td>
81	<td>9.1-RELEASE</td>	68	<td>9.3-RELEASE</td>
82	<td>RELENG_9_1</td>	69	<td>RELENG_9_3</td>
83	<td>packages-9-stable</td>	70	<td>packages-9-stable</td>
84	<td>December 31, 2014</td>	71	<td>December 31, 2016</td>
85	</tr>	72	</tr>
86	<tr>	73	<tr>
		74	<td>RELENG_10</td>
		75	<td>n/a</td>
		76	<td>RELENG_10_1</td>
		77	<td>packages-10-stable</td>
		78	<td>last release + 2 years</td>
		79	</tr>
		80	<tr>
		81	<td>RELENG_10_1</td>
		82	<td>10.1-RELEASE</td>
		83	<td>RELENG_10_1</td>
		84	<td>packages-10-stable</td>
		85	<td>December 31, 2016</td>
		86	</tr>
		87	<tr>
		88	<td>RELENG_10_2</td>
		89	<td>10.2-RELEASE</td>
		90	<td>RELENG_10_1</td>
		91	<td>packages-10-stable</td>
		92	<td>December 31, 2016</td>
		93	</tr>
		94	<tr>
		95	<td>RELENG_10_3</td>
		96	<td>10.3-RELEASE</td>
		97	<td>RELENG_10_1</td>
		98	<td>packages-10-stable</td>
		99	<td>April 30, 2018</td>
		100	</tr>
		101	<tr>
		102	<td>RELENG_11</td>
		103	<td>n/a</td>
		104	<td>RELENG_11_1</td>
		105	<td>packages-11-stable</td>
		106	<td>last release + 2 years</td>
		107	</tr>
		108	<tr>
87	<td>HEAD</td>	109	<td>HEAD</td>
88	<td>n/a</td>	110	<td>n/a</td>
89	<td>HEAD</td>	111	<td>HEAD</td>
90	<td>packages-10-current</td>	112	<td>packages-12-current</td>
91	<td>Best Effort</td>	113	<td>Best Effort</td>
92	</tr>	114	</tr>
93	</table>	115	</table>
94		116
95	<p>Older releases are not maintained, ports and packages may not be able	117	<p>Older releases are not maintained; ports and packages may not be able
96	to install or run. Users are strongly encouraged to upgrade to one of	118	to install or run. Users are strongly encouraged to upgrade to one of
97	the supported releases mentioned above.</p>	119	the supported releases mentioned above.</p>
98		120