[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ A ] [ next ]
The purpose of this document is to provide an overview of the recommended procedures and the available resources for Debian developers.
The procedures discussed within include how to become a maintainer (Applying to Become a Maintainer, Chapter 2); how to create new packages (New packages, Section 5.1) and how to upload packages (Uploading a package, Section 5.6); how to handle bug reports (Handling bugs, Section 5.8); how to move, remove, or orphan packages (Moving, removing, renaming, adopting, and orphaning packages, Section 5.9); how to port packages (Porting and being ported, Section 5.10); and how and when to do interim releases of other maintainers' packages (Non-Maintainer Uploads (NMUs), Section 5.11).
The resources discussed in this reference include the mailing lists (Mailing lists, Section 4.1) and servers (Debian machines, Section 4.4); a discussion of the structure of the Debian archive (The Debian archive, Section 4.6); explanation of the different servers which accept package uploads (Uploading to ftp-master, Section 5.6.1); and a discussion of resources which can help maintainers with the quality of their packages (Overview of Debian Maintainer Tools, Appendix A).
It should be clear that this reference does not discuss the technical details
of Debian packages nor how to generate them. Nor does this reference detail
the standards to which Debian software must comply. All of such information
can be found in the Debian Policy
Manual.
Furthermore, this document is not an expression of formal policy. It contains documentation for the Debian system and generally agreed-upon best practices. Thus, it is not what is called a ``normative'' document.
[ previous ] [ Contents ] [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] [ 6 ] [ 7 ] [ 8 ] [ A ] [ next ]
Debian Developer's Reference
[email protected]