<!ENTITY % dynamicdata SYSTEM "dynamic.ent" > %dynamicdata;
<!-- CVS revision of this document -->
- <!ENTITY cvs-rev "$Revision: 1.333 $">
+ <!ENTITY cvs-rev "$Revision: 1.334 $">
<!-- if you are translating this document, please notate the CVS
revision of the original developer's reference in cvs-en-rev -->
<p>
Send mail to &email-debian-devel; if you have any questions.
- <sect1 id="servers-cvs">The CVS server
-<!-- TODO: document svn.debian.org, arch.debian.org also -->
+ <sect1 id="servers-vcs">The VCS servers
<p>
-Our CVS server is located on <tt>cvs.debian.org</tt>.
+If you need to use a Version Control System for any of your Debian work,
+you can use one the existing repositories hosted on Alioth or you can
+request a new project and ask for the VCS repository of your choice.
+Alioth supports CVS (alioth.debian.org), Subversion
+(svn.debian.org), Arch (tla/baz, both on arch.debian.org), Bazaar
+(bzr.debian.org), Mercurial (hg.debian.org) and Git (git.debian.org).
+Checkout <url id="&url-alioth-pkg;"> if you plan
+to maintain packages in a VCS repository. See <ref id="alioth"> for
+information on the services provided by Alioth.
<p>
-If you need to use a publicly accessible CVS
-server, for instance, to help coordinate work on a package between
-many different developers, you can request a CVS area on the server.
- <p>
-Generally, <tt>cvs.debian.org</tt> offers a combination of local CVS
-access, anonymous client-server read-only access, and full
-client-server access through <prgn>ssh</prgn>. Also, the CVS area can
-be accessed read-only via the Web at <url id="&url-cvsweb;">.
- <p>
-To request a CVS area, send a request via email to
-&email-debian-admin;. Include the name of the requested CVS area,
-the Debian account that should own the CVS root area, and why you need it.
+Historically, Debian first used <tt>cvs.debian.org</tt> to host CVS
+repositories. But that service is deprecated in favor of Alioth.
+Only a few projects are still using it.
<sect1 id="dchroot">chroots to different distributions
<p>
all messages sent to these addresses must contain the <tt>X-PTS-Approved</tt>
header with a non-empty value.
+ <tag><tt>contact</tt>
+ <item>
+Mails sent to the maintainer through the *@packages.debian.org email
+aliases.
+
<tag><tt>summary</tt>
<item>
Regular summary emails about the package's status.
<tag><tt>cvs</tt>
<item>
-CVS commit notifications, if the package has a CVS repository and the
-maintainer has set up forwarding commit notifications to the PTS.
+VCS commit notifications, if the package has a VCS repository and the
+maintainer has set up forwarding of commit notifications to the PTS. The
+"cvs" name is historic, in most cases commit notifications will come
+from some other VCS like subversion or git.
<tag><tt>ddtp</tt>
<item>
<item><tt>bts-control</tt>: reply to mails sent to &email-bts-control;
<item><tt>summary</tt>: automatic summary mails about the state of a
package
- <item><tt>cvs</tt>: notification of CVS commits
+ <item><tt>contact</tt>: mails sent to the maintainer through the
+ *@packages.debian.org aliases
+ <item><tt>cvs</tt>: notification of VCS commits
<item><tt>ddtp</tt>: translations of descriptions and debconf templates
<item><tt>derivatives</tt>: changes made on the package by derivative
distributions
X-Loop: dpkg@&pts-host;
X-PTS-Package: dpkg
X-PTS-Keyword: upload-source
-X-Unsubscribe: echo 'unsubscribe dpkg' | mail pts@qa.debian.org
+List-Unsubscribe: <mailto:pts@qa.debian.org?body=unsubscribe+dpkg>
</example>
- <sect1 id="pts-cvs-commit">Forwarding CVS commits in the PTS
+ <sect1 id="pts-vcs-commit">Forwarding VCS commits in the PTS
<p>
-If you use a publicly accessible CVS repository for maintaining
+If you use a publicly accessible VCS repository for maintaining
your Debian package, you may want to forward the commit notification
to the PTS so that the subscribers (and possible co-maintainers) can
closely follow the package's evolution.
<p>
-Once you set up the CVS repository to generate commit notifications,
+Once you set up the VCS repository to generate commit notifications,
you just have to make sure it sends a copy of those mails
to <tt><var>sourcepackage</var>_cvs@&pts-host;</tt>. Only the people
who accept the <em>cvs</em> keyword will receive these notifications.
+Note that the mail need to be sent from a <tt>debian.org</tt> machine,
+otherwise you'll have to add the <tt>X-PTS-Approved: 1</tt> header.
+ <p>
+For Subversion repositories, the usage of svnmailer is recommended.
+See <url id="&url-alioth-pkg;"> for an example on how to do it.
<sect1 id="pts-web">The PTS web interface
<p>
you don't forget any open bugs, and so that you don't forget which
packages are your responsibility.
- <sect id="alioth">Debian *Forge: Alioth
+ <sect id="alioth">Debian's GForge installation: Alioth
<p>
-Alioth is a fairly new Debian service, based on a slightly modified version
-of the GForge software (which evolved from SourceForge). This software
-offers developers access to easy-to-use tools such as bug trackers, patch
+Alioth is a Debian service based on a slightly modified version of the
+GForge software (which evolved from SourceForge). This software offers
+developers access to easy-to-use tools such as bug trackers, patch
manager, project/task managers, file hosting services, mailing lists, CVS
repositories etc. All these tools are managed via a web interface.
<p>
It is intended to provide facilities to free software projects backed or led
by Debian, facilitate contributions from external developers to projects
started by Debian, and help projects whose goals are the promotion of Debian
-or its derivatives.
+or its derivatives. It's heavily used by many Debian teams and provides
+hosting for all sorts of VCS repositories.
<p>
All Debian developers automatically have an account on Alioth.
They can activate it by using the recover password facility.
External developers can request guest accounts on Alioth.
<p>
-For more information please visit <url id="&url-alioth;">.
+For more information please visit the following links:
+<list>
+<item><url id="&url-alioth-wiki;">
+<item><url id="&url-alioth-faq;">
+<item><url id="&url-alioth-pkg;">
+<item><url id="&url-alioth;">
+</list>
<sect id="developer-misc">Goodies for Developers
<p>
~ianmdlvl / developers-reference.git / commitdiff