1 developers-reference (2.5.0.6) unstable; urgency=low
3 * typo correction from Christian Hudon (closes Bug#32052)
4 * update number of available packages
6 -- Adam Di Carlo <aph@debian.org> Tue, 19 Jan 1999 00:47:25 -0500
8 developers-reference (2.5.0.5) unstable; urgency=low
10 * add version.ent to docdir, needed to reconstruct from SGML
12 -- Adam Di Carlo <aph@debian.org> Tue, 29 Dec 1998 02:42:50 -0500
14 developers-reference (2.5.0.4) unstable; urgency=low
16 * not officially released
17 * more spelling corrections
18 * s/ppc/powerpc/ (thanks, James Troup)
20 -- Adam Di Carlo <aph@debian.org> Fri, 18 Dec 1998 00:07:40 -0500
22 developers-reference (2.5.0.3) unstable; urgency=low
24 * not officially released
25 * Sec. "Removing a package from Incoming": tiny section added
26 * some PGP-centricity removed
27 * Sec. "Adopting a package": point out that hijacking packages is not ok
28 * Ch. "Non-Maintainer Uploads (NMUs) and Porters": change 'NMU' to
29 'source NMU', 'port' to 'binary NMU', shorten the window for porters a
30 tad; fix spelling; stress that non-maintainer patches must be
31 non-disruptive and that aesthetic issues are not suitable for fixing
32 by non-maintainers; other fixes as suggested by interested parties
34 -- Adam Di Carlo <aph@debian.org> Wed, 25 Nov 1998 00:01:27 -0500
36 developers-reference (2.5.0.2) frozen unstable; urgency=low
38 * not officially released
39 * maintainer name change (but it's still me)
40 * Ch. "Non-Maintainer Uploads (NMUs) and Porters": new chapter
41 discussing NMUs and porters; Section "Interim Releases" integrated out
42 of existance. New TOC for this section is:
43 * 6 Non-Maintainer Uploads (NMUs) and Porters
44 + 6.1 Who can do a port or an NMU
45 + 6.2 When to do a port or an NMU
46 o 6.2.1 When to do an NMU if you are a porter
47 + 6.3 How to do an NMU
48 o 6.3.1 NMU version numbering
49 o 6.3.2 NMUs must create a changelog entry
50 o 6.3.3 NMUs must send patches, if any, to the BTS
51 o 6.3.4 Building the NMU
52 + 6.4 Guidelines for Porters
54 * Sec. "Maintainer changes": renamed to "Adopting a package" and moved
55 to Chapter "Moving, Removing, Renaming, Adopting, and Orphaning
57 * Sec. "Reporting lots of bugs at once": more forcefully deprecate this
59 * Sec. "Adopting a package": mention that the BTS maintainer update can
60 take a couple of weeks
61 * Sec. "Overview of Debian Maintainer Tools": give credit where credit
62 is due and attribute current maintainers; add `apt'; add `quinn-diff';
63 add mention of as yet unreleased 'buildd' package, since I'm so
64 excited about it and can't wait
65 * Sec. "Removing packages": talk about how apt-cache can be used to look
66 at reverse depends, a good step to take prior to removing a package
68 * show *full* TOC, including sect2
69 * of course the obligatory typo, grammar, and spelling corrections
71 * Makefile: small changes to accomodate DDP autobuild
72 * debian/dirs: obsolete, removed
73 * debian/rules: use changelog date for SGML timestamping, not current date
75 -- Adam Di Carlo <aph@debian.org> Fri, 20 Nov 1998 12:27:53 -0500
77 developers-reference (2.5.0) frozen unstable; urgency=low
79 * move to 3-level version number:
80 top-level version number probably won't change for a whil, it is the
81 "major", the second-level number means significant content changes,
82 and the third-level change means corrections and minor improvements.
83 Since this version has significant content changes, we are now 2.5.0.
84 Since I'm going to put porter instructions in the next major rev, that
87 * use new <package> tag where appropriate (Ardo, you rock)
88 * replace 'm86k' with 'm68k'
89 * rename 'Whirlwind Tour of ...' section to 'Overview of ...' (suggested
91 * typos and "red-pen" corrections, fix cosmetic problems in PostScript
93 * remove the one case I use an URL fragment identifier, since
94 debiandoc-sgml doesn't like it (bug filed against debiandoc-sgml)
95 * debian/rules: cosmetic cleanups, loosen check for root
96 * debian/rules: build PostScript version during build, since it's nice
97 to have all my debiandoc2* scripts together
98 * debian/control: policy compliant to 2.5.0
100 * advise against uploading when a package has lintian problems of
102 * "Mailing Lists and Servers":
103 - "The master server": mention how master is the home of the BTS;
104 mention how users need to take care with their accounts on master
105 - "The WWW servers": fill in www.debian.org, first pass, and discuss
106 how to put up your own web pages on va or master
107 - "The CVS server": new section added
108 - "Mirrors of Debian servers": new section added; point to info about
110 * "Applying to Become a Maintainer": do not advise resending initial
111 application; instead, simply mail a followup asking new maintainers
112 whether they go the initial application (closes Bug #28739); mention
113 that calls usually come in the evening; mention that if you use PGP
114 v5, you need to generate an RSA key (right?); clarify our intentions
116 * "Release code names": Debian 2.2 is 'potato'
117 * "Distribution directories": give concrete examples, hopefully making
118 it clearer where to look in Debian archives for specific stuff;
119 mention that old distributions are moved to archive servers (is there
120 a canonical location?)
121 * "The override file": new section, added under "Notification that a new
122 package has been installed"; fill it out quite a bit
123 * "Uploading to *": reiterate thrice not to upload export
124 controlled-software to master, or the European queues on erlangen and
126 * "Picking a distribution": section broken out from "Generating the
128 * "Uploading to frozen": new section, almost straight from Brian White
129 (hope you don't mind!) -- isn't that topical?
130 * "Interim releases": if you NMU a new upstream version (0.1), run
131 'dpkg-buildpackage -sa'
133 -- Adam P. Harris <aph@debian.org> Thu, 12 Nov 1998 00:03:43 -0500
135 developers-reference (2.4.1.5) unstable; urgency=low
137 * Fix instructions for new maintainers, incorporating the actual text
138 sent to prospective new maintainers. Improve this text a bit for
139 readability, coverage, and organization. Significant changes were
140 patched back to the new-maintainers group, if they care to use
141 them. (closes Bug#26948)
142 * Add an introductory "Scope" chapter which helps delineate what should
143 and should not be included in this Reference.
144 * Add a new chapter, "Whirlwind Tour of Debian Maintainer Tools". Let
145 me know what useful tools I forgot -- remember, Debian-specific
146 maintainer tools only!
147 * Add discussion of the "experimental" distribution, culled from an email
148 from Guy Maor on debian-devel.
149 * Incorporated suggestions from Branden Robinson (closes Bug#27211).
150 * Point to doc-debian's mailing list instructions where relevant.
151 * Made references to online documentation into URLs where possible.
152 * Little corrections here and there.
153 * add a Makefile for use in the DDP manual hierarchy
154 * debian/rules: comment out my 'source-depends' hack; it's just slowing
157 -- Adam P. Harris <aph@debian.org> Thu, 1 Oct 1998 03:42:43 -0400
159 developers-reference (2.4.1.4) unstable; urgency=low
161 * fill in Section "The master server" a bit; other servers to follow
162 * in Section "Distribution directories", mention that distributions
163 are always in 'dists' subdir of the Debian archive; talk about
165 * in Section "Release code names", talk about 'sid' a bit
166 * in Section "Interim releases", talk about how non-maintainers should
167 use the BTS, and bug severity "fixed" (closes Bug#17524)
168 * in Section "Generating the changes file", talk about how to set the
169 distribution in the debian/changelog file (i.e., "frozen unstable")
170 * add a new Section "Checking the package prior to upload" to Section
171 "Uploading a package", mentioning lintian and other tests one should
172 do prior to uploading
173 * add new Section "Notification that a new package has been installed"
174 in Section "Uploading a package", talking about dinstall and the
176 * add new Sections "Moving packages", "Removing packages", "Replacing or
177 renaming packages", and "Orphaning a package" (closes Bug#26650)
178 * add new Section "Bugs in your packages", talking about maintainer
179 duties with respect to bugs
180 * add new Section "Lintian reports" under "Handling bugs reports",
181 talking about how maintainers should check their packages with lintian
182 every now and then, alternatively pointing them to the lintian web
184 * clarify, a bit, the use of "section" and "subsection", bringing it
185 into line with the usage in the Policy Manual and Packaging Manual
186 * grammar and markup changes throughout
187 * debian/rules: added a crude source-depends rule, which renders more
188 explicit what is used to build this package
190 -- Adam P. Harris <aph@debian.org> Mon, 21 Sep 1998 00:51:46 -0400
192 developers-reference (2.4.1.3) unstable; urgency=low
195 * version number and date are automatically populated now
196 * changed doc-base section to "debian"
197 * debian/rules: better abstraction and organization
198 * reformat SGML like I happen to like it
199 * utilize the new URL tag
200 * build PostScript on letter size, I hear thats better for A4 and US
203 -- Adam P. Harris <aph@debian.org> Thu, 16 Jul 1998 00:52:35 -0400
205 developers-reference (2.4.1.2) frozen unstable; urgency=low
207 * non-maintainer release
208 * rebuilt since HTML versions of Chapters 1 and 2 were truncated
209 (important bug, no number yet, bugs.debian.org isn't working;
210 regardless, this should go in hamm because a broken developers
211 reference won't win us many friends in hamm, and after all, it's just
212 text, it can't hurt you.)
213 * no content changes, except that the version number in the SGML file
214 reflect this packages version number
215 * debian/rule: clean is cleaner now
217 -- Adam P. Harris <aph@debian.org> Tue, 16 Jun 1998 01:35:39 -0400
219 developers-reference (2.4.1.1) frozen unstable; urgency=low
223 -- Christian Schwarz <schwarz@debian.org> Thu, 14 May 1998 21:56:36 +0200
225 developers-reference (2.4.1.0) frozen unstable; urgency=low
227 * New version numbering scheme:
229 - The version numbers are independent of dpkg now, but all policy
230 manuals (the Debian Policy Manual, the Debian Packaging Manual, and
231 the Debian Developer's Reference) share the same version numbering
234 - The first three digits of the version number specify the
235 `Standards-Version.' This number is incremented with each policy
236 change. The fourth digit represents the `patch-level,' which may
237 differ between the manuals.
239 If only the patch-level digit is incremented, no changes in policy
240 have been made, except bug fixes and clarifications. Packages only
241 have to specify the first three digits of the version number in the
242 `Standards-Version' field of their source packages.
244 * Uploaded to frozen and unstable. This is a documentation-only
245 package and the changes to the manual are relevant for hamm.
247 * No changes to the Developer's Reference
249 -- Christian Schwarz <schwarz@debian.org> Mon, 13 Apr 1998 17:54:43 +0200
251 developers-reference (0.5) unstable; urgency=low
253 * Changes to the Developer's Reference:
255 - Changed section 1.2 Registering as a Debian developer:
256 + signatures from formal certification service are _NOT_ accepted
258 + images of ID documents have to be PGP or RSA signed
259 (as requested by James Troup)
261 - Use current date instead of <date> in manual
263 * Updated FSF's address (reported by Lintian)
265 -- Christian Schwarz <schwarz@debian.org> Sat, 7 Mar 1998 13:52:15 +0100
267 developers-reference (0.4) unstable; urgency=low
269 * Changes to the Developer's Reference:
271 - Renamed chapter 4 into `Package uploads'
273 - New section 4.2.5 Uploading to the non-us server
275 - Changed section 4.4 Interim releases:
276 + non-maintainer releases should not close bugs
277 + normal maintainer must at least read the patch provided with
278 the non-maintainer release
280 - New chapter 5 Handling bug reports:
281 + when reporting more then 10 bugs on the same topic, a message
282 has to be sent to debian-devel and the `maintonly' address
285 - Lots of typos fixed
287 * Compressed SGML source code
289 * Added support for doc-base to register the Developer's Reference
290 to the online documentation systems dwww and dhelp
292 * Upgraded to standards version 2.4.0.0 (no changes)
294 -- Christian Schwarz <schwarz@debian.org> Fri, 30 Jan 1998 21:58:34 +0100
296 developers-reference (0.3) unstable; urgency=low
298 * Put lost sections from Policy Manual 2.1.3.3 back in:
299 - Generating the changes file (for uploads)
300 - Announcing package uploads
301 * New section about Debian Mentors
302 * debian/rules: Don't use debstd anymore
303 * debian/rules: Compress changelog file (fixes:#15441)
304 * Fixed link to WNPP list (fixes:#16201)
305 * Added menu entry (fixes:#15708)
307 -- Christian Schwarz <schwarz@debian.org> Wed, 24 Dec 1997 13:54:33 +0100
309 developers-reference (0.2) unstable; urgency=low
311 * New chapter about `The Debian Archive' describing the structure
312 of our FTP server and the development process
313 * Added note that new maintainers have to read the Social Contract
314 and have to know where to find the Policy and Packaging Manuals
315 * PGP key ring is not distributed via dpkg but in doc/ of the FTP
317 * Added note that cross posting between Debian lists is depreciated
318 * New list of advantages why new packages should be discussed on
319 debian-devel before they are uploaded
320 * Added section about how packages are uploaded
321 * Added note that the Security Managers may do interim releases without
322 contacting the maintainer
323 * Removed chapter about bug tracking system (will be included in
324 a new manual released soon)
326 * Include SGML source in package
327 * Don't use `2-up' style for PostScript version
328 * Upgraded to Standards 2.3.0.1
330 -- Christian Schwarz <schwarz@debian.org> Sun, 2 Nov 1997 20:53:26 +0100
332 developers-reference (0.1) unstable; urgency=low
336 -- Christian Schwarz <schwarz@debian.org> Tue, 8 Jul 1997 00:19:49 +0200
339 mode: debian-changelog