+developers-reference (2.5.0.3) unstable; urgency=low
+
+ * not officially released
+ * Sec. "Removing a package from Incoming": tiny section added
+ * some PGP-centricity removed
+ * Sec. "Adopting a package": point out that hijacking packages is not ok
+ * Ch. "Non-Maintainer Uploads (NMUs) and Porters": change 'NMU' to
+ 'source NMU', 'port' to 'binary NMU', shorten the window for porters a
+ tad; fix spelling; stress that non-maintainer patches must be
+ non-disruptive and that aesthetic issues are not suitable for fixing
+ by non-maintainers; other fixes as suggested by interested parties
+
+ -- Adam Di Carlo <aph@debian.org> Wed, 25 Nov 1998 00:01:27 -0500
+
+developers-reference (2.5.0.2) frozen unstable; urgency=low
+
+ * not officially released
+ * maintainer name change (but it's still me)
+ * Ch. "Non-Maintainer Uploads (NMUs) and Porters": new chapter
+ discussing NMUs and porters; Section "Interim Releases" integrated out
+ of existance. New TOC for this section is:
+ * 6 Non-Maintainer Uploads (NMUs) and Porters
+ + 6.1 Who can do a port or an NMU
+ + 6.2 When to do a port or an NMU
+ o 6.2.1 When to do an NMU if you are a porter
+ + 6.3 How to do an NMU
+ o 6.3.1 NMU version numbering
+ o 6.3.2 NMUs must create a changelog entry
+ o 6.3.3 NMUs must send patches, if any, to the BTS
+ o 6.3.4 Building the NMU
+ + 6.4 Guidelines for Porters
+
+ * Sec. "Maintainer changes": renamed to "Adopting a package" and moved
+ to Chapter "Moving, Removing, Renaming, Adopting, and Orphaning
+ Packages".
+ * Sec. "Reporting lots of bugs at once": more forcefully deprecate this
+ practice
+ * Sec. "Adopting a package": mention that the BTS maintainer update can
+ take a couple of weeks
+ * Sec. "Overview of Debian Maintainer Tools": give credit where credit
+ is due and attribute current maintainers; add `apt'; add `quinn-diff';
+ add mention of as yet unreleased 'buildd' package, since I'm so
+ excited about it and can't wait
+ * Sec. "Removing packages": talk about how apt-cache can be used to look
+ at reverse depends, a good step to take prior to removing a package
+ from the archive
+ * show *full* TOC, including sect2
+ * of course the obligatory typo, grammar, and spelling corrections
+
+ * Makefile: small changes to accomodate DDP autobuild
+ * debian/dirs: obsolete, removed
+ * debian/rules: use changelog date for SGML timestamping, not current date
+
+ -- Adam Di Carlo <aph@debian.org> Fri, 20 Nov 1998 12:27:53 -0500
+
+developers-reference (2.5.0) frozen unstable; urgency=low
+
+ * move to 3-level version number:
+ top-level version number probably won't change for a whil, it is the
+ "major", the second-level number means significant content changes,
+ and the third-level change means corrections and minor improvements.
+ Since this version has significant content changes, we are now 2.5.0.
+ Since I'm going to put porter instructions in the next major rev, that
+ will be 2.6.0...
+
+ * use new <package> tag where appropriate (Ardo, you rock)
+ * replace 'm86k' with 'm68k'
+ * rename 'Whirlwind Tour of ...' section to 'Overview of ...' (suggested
+ by James Troup)
+ * typos and "red-pen" corrections, fix cosmetic problems in PostScript
+ version
+ * remove the one case I use an URL fragment identifier, since
+ debiandoc-sgml doesn't like it (bug filed against debiandoc-sgml)
+ * debian/rules: cosmetic cleanups, loosen check for root
+ * debian/rules: build PostScript version during build, since it's nice
+ to have all my debiandoc2* scripts together
+ * debian/control: policy compliant to 2.5.0
+
+ * advise against uploading when a package has lintian problems of
+ severity 'E'
+ * "Mailing Lists and Servers":
+ - "The master server": mention how master is the home of the BTS;
+ mention how users need to take care with their accounts on master
+ - "The WWW servers": fill in www.debian.org, first pass, and discuss
+ how to put up your own web pages on va or master
+ - "The CVS server": new section added
+ - "Mirrors of Debian servers": new section added; point to info about
+ how to mirror
+ * "Applying to Become a Maintainer": do not advise resending initial
+ application; instead, simply mail a followup asking new maintainers
+ whether they go the initial application (closes Bug #28739); mention
+ that calls usually come in the evening; mention that if you use PGP
+ v5, you need to generate an RSA key (right?); clarify our intentions
+ with respect to GPG.
+ * "Release code names": Debian 2.2 is 'potato'
+ * "Distribution directories": give concrete examples, hopefully making
+ it clearer where to look in Debian archives for specific stuff;
+ mention that old distributions are moved to archive servers (is there
+ a canonical location?)
+ * "The override file": new section, added under "Notification that a new
+ package has been installed"; fill it out quite a bit
+ * "Uploading to *": reiterate thrice not to upload export
+ controlled-software to master, or the European queues on erlangen and
+ chiark
+ * "Picking a distribution": section broken out from "Generating the
+ changes file"
+ * "Uploading to frozen": new section, almost straight from Brian White
+ (hope you don't mind!) -- isn't that topical?
+ * "Interim releases": if you NMU a new upstream version (0.1), run
+ 'dpkg-buildpackage -sa'
+
+ -- Adam P. Harris <aph@debian.org> Thu, 12 Nov 1998 00:03:43 -0500
+
developers-reference (2.4.1.5) unstable; urgency=low
* Fix instructions for new maintainers, incorporating the actual text