* Remove Satoshi as Ports Wraith

* Remove jkh as RE
* Add steve, murray, rwatson, jhb as RE team.

Submitted by:	jkh (commit_prep.pl is still being temperamental)
This commit is contained in:
Murray Stokely 2001-12-10 08:36:47 +00:00
parent 939519687c
commit b17f8fa162
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=11388
2 changed files with 21 additions and 29 deletions

View file

@ -522,11 +522,11 @@
</itemizedlist>
<para>You will almost certainly get a conflict because
of the <literal>$Id: article.sgml,v 1.91 2001-12-01 18:29:32 jdp Exp $</literal> (or in FreeBSD's case,
<literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you will have to edit
of the <literal>$Id: article.sgml,v 1.92 2001-12-10 08:36:47 murray Exp $</literal> (or in FreeBSD's case,
<literal>$<!-- stop expansion -->FreeBSD<!-- stop expansion -->$</literal>) lines, so you will have to edit
the file to resolve the conflict (remove the marker lines and
the second <literal>$Id: article.sgml,v 1.91 2001-12-01 18:29:32 jdp Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.91 2001-12-01 18:29:32 jdp Exp $</literal> line intact).</para>
the second <literal>$Id: article.sgml,v 1.92 2001-12-10 08:36:47 murray Exp $</literal> line, leaving the original
<literal>$Id: article.sgml,v 1.92 2001-12-10 08:36:47 murray Exp $</literal> line intact).</para>
</listitem>
<listitem>
@ -1075,18 +1075,6 @@ docs:Documentation Bug:nik:</programlisting>
and by no means all-inclusively, these are:</para>
<variablelist>
<varlistentry>
<term>&a.asami;</term>
<listitem>
<para>Satoshi is the Ports Wraith, meaning that he has
ultimate authority over any modifications to the ports
collection or the ports skeleton makefiles. He is also
the one responsible for administering ports freezes before
the releases.</para>
</listitem>
</varlistentry>
<varlistentry>
<term>&a.nik;</term>
@ -1150,19 +1138,21 @@ docs:Documentation Bug:nik:</programlisting>
</varlistentry>
<varlistentry>
<term>&a.jkh;</term>
<listitem>
<para>Jordan is the release engineer. He is responsible for
setting release deadlines and controlling the release
process. During code freezes, he also has final authority
on all changes to the system for whichever branch is
pending release status. If there is something you want
merged from &os.current; to
&os.stable; (whatever values those may have
at any given time), he is also the one to talk to about
it.</para>
</listitem>
<term>&a.murray;</term>
<term>&a.steve;</term>
<term>&a.rwatson;</term>
<term>&a.jhb;</term>
<listitem>
<para>These are the members of the &a.re;. This team is
responsible for setting release deadlines and controlling
the release process. During code freezes, the release
engineers have final authority on all changes to the
system for whichever branch is pending release status. If
there is something you want merged from &os.current; to
&os.stable; (whatever values those may have at any given
time), these are the people to talk to about it.</para>
</listitem>
</varlistentry>
<varlistentry>

View file

@ -526,6 +526,8 @@
<!ENTITY a.pst "Paul Traina <email>pst@FreeBSD.org</email>">
<!ENTITY a.re "Release Engineering Team <email>re@FreeBSD.org</email>">
<!ENTITY a.reg "Jeremy Lea <email>reg@FreeBSD.org</email>">
<!ENTITY a.rgrimes "Rodney Grimes <email>rgrimes@FreeBSD.org</email>">