Attachment #187191 for bug #213056





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


	X11 servers, GNOME, KDE, autotools, and so forth</p></li>
  <li><p>changes that change the "accepted best practice" for
	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>


  commits in certain unusual cases, such as: commits that in their
  opinion destabilize the Ports Collection; violate the
  Principle Of Least Astonishment for FreeBSD's users; or in cases
  of inter-committer disputes that cannot 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

  their status and interest in continuing to work with the ports tree.
  Committers who do not respond to such email, or who respond in the
  negative, have their commit bits reclaimed for safekeeping.
  Currently, this period is one year.</p>

<p>In unusual cases it may become necessary to remove Ports Committers
  for other reasons.  This will only be done after serious deliberation,





<p>The time limit for a maintainer to respond to a PR is two weeks.
  After that period, if it is a minor change, any ports committer can
  commit the change.  If it is a major change (e.g., would require a
  regression run), please contact portmgr first.</p>

<p>We have an add-on to the Problem Reports database known as the auto-assigner,
  which attempts to automatically notify maintainers of PRs; however,
  it depends on the Summary containing category/portname.  In general,
  various people attempt to catch and fix cases where it does not work,
  but you should not assume so.  Therefore, please
  check to see whether or not the maintainer knows about the PR before


<p>This period may be shortened by portmgr if the email address returns
  with a hard bounce.  In this case, it is probably desirable to reset
  all the maintainer's ports and check the status of any PRs.</p>
  to 'open'.</p>

<a name="commit_privileges"></a>
<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

  </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>


Return to bug 213056

Lines 31-37 Link Here

(-)en_US.ISO8859-1/htdocs/portmgr/policies.xml (-8 / +8 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	<a href="https://pkg-status.freebsd.org">ports building cluster</a>.
		35	These are termed experimental builds (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 41-53 Link Here
41	X11 servers, GNOME, KDE, autotools, and so forth</p></li>	42	X11 servers, GNOME, KDE, autotools, and so forth</p></li>
42	<li><p>changes that change the "accepted best practice" for	43	<li><p>changes that change the "accepted best practice" for
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 59-69 Link Here
59	commits in certain unusual cases, such as: commits that in their	60	commits in certain unusual cases, such as: commits that in their
60	opinion destabilize the Ports Collection; violate the	61	opinion destabilize the Ports Collection; violate the
61	Principle Of Least Astonishment for FreeBSD's users; or in cases	62	Principle Of Least Astonishment for FreeBSD's users; or in cases
62	of inter-committer disputes that can not be solved among the	63	of inter-committer disputes that cannot 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 167-173 Link Here
167	their status and interest in continuing to work with the ports tree.	167	their status and interest in continuing to work with the ports tree.
168	Committers who do not respond to such email, or who respond in the	168	Committers who do not respond to such email, or who respond in the
169	negative, have their commit bits reclaimed for safekeeping.	169	negative, have their commit bits reclaimed for safekeeping.
170	Currrently, this period is one year.</p>	170	Currently, this period is one year.</p>
171		171
172	<p>In unusual cases it may become necessary to remove Ports Committers	172	<p>In unusual cases it may become necessary to remove Ports Committers
173	for other reasons. This will only be done after serious deliberation,	173	for other reasons. This will only be done after serious deliberation,

Lines 21-32 Link Here

(-)en_US.ISO8859-1/htdocs/portmgr/policies_contributors.xml (-4 / +3 lines)
21		21
22	<p>The time limit for a maintainer to respond to a PR is two weeks.	22	<p>The time limit for a maintainer to respond to a PR is two weeks.
23	After that period, if it is a minor change, any ports committer can	23	After that period, if it is a minor change, any ports committer can
24	commit the change. If it is a major change (e.g. would require a	24	commit the change. If it is a major change (e.g., would require a
25	regression run), please contact portmgr first.</p>	25	regression run), please contact portmgr first.</p>
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>

Lines 14-20 Link Here

(-)en_US.ISO8859-1/htdocs/portmgr/policies_eol.xml (-4 / +5 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 128-134 Link Here
128	</tr>	129	</tr>
129	</table>	130	</table>
130		131
131	<p>Older releases are not maintained, ports and packages may not be able	132	<p>Older releases are not maintained; ports and packages may not be able
132	to install or run. Users are strongly encouraged to upgrade to one of	133	to install or run. Users are strongly encouraged to upgrade to one of
133	the supported releases mentioned above.</p>	134	the supported releases mentioned above.</p>
134		135