[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded developers-reference 2.4.1.4 (source all) to master



This version contains some major textual additions and changes.  I
have not really gone over it for wording or grammar, so I'm sure there
are some grevious typo problems.

I still need to add a "Scope" section talking about the scope of this
document.  Many people find it confusing how our core documentation is
broken up.  I sympathize with this, although I do think the current
breakup has merit.  Richard Braakman has asked me to put pointers to
other tools likely to be of interest to maintainers, which I think is
a bit off-scope but I'm amenable to do so.

At any rate, I'd gladly accept emails or bugs for problems and missing
features.  It's up to us, the more experienced developers, to make
Debian a bit more friendly for new maintainers.  Documentation such as
this can also help cut down on FAQs to the mailing lists, and help us
turn around release more quickly.
-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.5
Date: Mon, 21 Sep 1998 00:51:46 -0400
Source: developers-reference
Binary: developers-reference
Architecture: source all
Version: 2.4.1.4
Distribution: unstable
Urgency: low
Maintainer: Adam P. Harris <aph@debian.org>
Description: 
 developers-reference - Debian Developer's Reference
Changes: 
 developers-reference (2.4.1.4) unstable; urgency=low
 .
   * fill in Section "The master server" a bit; other servers to follow
   * in Section "Distribution directories", mention that distributions
     are always in 'dists' subdir of the Debian archive; talk about
     'proposed-updates'
   * in Section "Release code names", talk about 'sid' a bit
   * in Section "Interim releases", talk about how non-maintainers should
     use the BTS, and bug severity "fixed" (closes Bug#17524)
   * in Section "Generating the changes file", talk about how to set the
     distribution in the debian/changelog file (i.e., "frozen unstable")
   * add a new Section "Checking the package prior to upload" to Section
     "Uploading a package", mentioning lintian and other tests one should
     do prior to uploading
   * add new Section "Notification that a new package has been installed"
     in Section "Uploading a package", talking about dinstall and the
     override file a bit
   * add new Sections "Moving packages", "Removing packages", "Replacing or
     renaming packages", and "Orphaning a package" (closes Bug#26650)
   * add new Section "Bugs in your packages", talking about maintainer
     duties with respect to bugs
   * add new Section "Lintian reports" under "Handling bugs reports",
     talking about how maintainers should check their packages with lintian
     every now and then, alternatively pointing them to the lintian web
     pages
   * clarify, a bit, the use of "section" and "subsection", bringing it
     into line with the usage in the Policy Manual and Packaging Manual
   * grammar and markup changes throughout
   * debian/rules: added a crude source-depends rule, which renders more
     explicit what is used to build this package
Files: 
 4fa355222b06adb4e66e61f836e2e749 588 doc extra developers-reference_2.4.1.4.dsc
 22e41ada67151d87bb64a5b6a90068e1 18260 doc extra developers-reference_2.4.1.4.tar.gz
 667952d70cf8b14cf8fca1ab7fb6d774 47410 doc extra developers-reference_2.4.1.4_all.deb
 ba2ab2f04550c7b23eafa6d2f4a8865d 40209 byhand - developers-reference.ps.gz
 b3a30e14bd288ede9292fe1bcd0f31e6 14742 byhand - developers-reference.html.tar.gz
 f0f5d5e938552332603147eb4a203ae7 9990 byhand - developers-reference.text.gz

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv

iQCVAwUBNgYMiY/8QF79WmfNAQG1qQQAwvm7fY9R0s1SKvrZ58IKtNXZ0AL2JZK+
vPg+uStOhnaQfWGzTUlG0qbMxW99jGy/CN3KeAqBFiHDfhoDZGyGHalIPIgyssS4
QLqti8crzOSokwzhKseR+3k6h5ZN+2rnixFd+3ChjW8Z+cubXoaimY6ZlwWAjb7Q
8trBmH6zCN0=
=GvTi
-----END PGP SIGNATURE-----


Reply to: