<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
- <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
+ <!ENTITY % commondata SYSTEM "common.ent" > %commondata;
]>
<chapter id="beyond-pkging">
<title>Beyond Packaging</title>
</para>
<para>
If you report more than 10 bugs on the same topic at once, it is recommended
-that you send a message to <email>debian-devel@&lists-host;</email>
-describing your intention before submitting the report, and mentioning the fact
-in the subject of your mail. This will allow other developers to verify that
-the bug is a real problem. In addition, it will help prevent a situation in
-which several maintainers start filing the same bug report simultaneously.
+that you send a message to &email-debian-devel; describing
+your intention before submitting the report, and mentioning the fact in the
+subject of your mail. This will allow other developers to verify that the bug
+is a real problem. In addition, it will help prevent a situation in which
+several maintainers start filing the same bug report simultaneously.
</para>
<para>
Please use the programms <command>dd-list</command> and if appropriate
<command>whodepends</command> (from the package devscripts) to generate a list
of all affected packages, and include the output in your mail to
-<email>debian-devel@&lists-host;</email>.
+&email-debian-devel;.
</para>
<para>
Note that when sending lots of bugs on the same subject, you should send the
should consider orphaning some of your packages (see <xref
linkend="orphaning"/> ). Alternatively, you may ask the help of other people
in order to catch up with the backlog of bugs that you have (you can ask for
-help on <email>debian-qa@&lists-host;</email> or
-<email>debian-devel@&lists-host;</email>). At the same time, you can look
-for co-maintainers (see <xref linkend="collaborative-maint"/> ).
+help on &email-debian-qa; or
+&email-debian-devel;). At the same time, you can look for
+co-maintainers (see <xref linkend="collaborative-maint"/> ).
</para>
</section>
<para>
From time to time the QA group organizes bug squashing parties to get rid of as
many problems as possible. They are announced on
-<email>debian-devel-announce@&lists-host;</email> and the announcement
-explains which area will be the focus of the party: usually they focus on
-release critical bugs but it may happen that they decide to help finish a major
-upgrade (like a new perl version which requires recompilation of all the binary
+&email-debian-devel-announce; and the announcement explains
+which area will be the focus of the party: usually they focus on release
+critical bugs but it may happen that they decide to help finish a major upgrade
+(like a new perl version which requires recompilation of all the binary
modules).
</para>
<para>
happened to the person they sponsored.
</para>
<para>
-It is also allowed to post a query to
-<email>debian-devel@&lists-host;</email>, asking if anyone is aware of the
-whereabouts of the missing maintainer. Please Cc: the person in question.
+It is also allowed to post a query to &email-debian-devel;,
+asking if anyone is aware of the whereabouts of the missing maintainer. Please
+Cc: the person in question.
</para>
<para>
Once you have gathered all of this, you can contact
-<email>mia@qa.debian.org</email>. People on this alias will use the
+&email-mia;. People on this alias will use the
information you provide in order to decide how to proceed. For example, they
might orphan one or all of the packages of the maintainer. If a package has
been NMUed, they might prefer to contact the NMUer before orphaning the package
If you are interested in working in the MIA team, please have a look at the
README file in /org/qa.debian.org/mia on qa.debian.org where the technical
details and the MIA procedures are documented and contact
-<email>mia@qa.debian.org</email>.
+&email-mia;.
</para>
</section>
<title>Advocating new developers</title>
<para>
See the page about <ulink
-url="&url-devel-docs;join/nm-advocate">advocating a prospective
+url="&url-newmaint-advocate;">advocating a prospective
developer</ulink> at the Debian web site.
</para>
</section>
<section id="s7.5.4">
<title>Handling new maintainer applications</title>
<para>
-Please see <ulink
-url="&url-devel-docs;join/nm-amchecklist">Checklist for Application
-Managers</ulink> at the Debian web site.
+Please see <ulink url="&url-newmaint-amchecklist;">Checklist
+for Application Managers</ulink> at the Debian web site.
</para>
</section>
~ianmdlvl / developers-reference.git / blobdiff