NMU Policy

	NMUs should be made to assist a package's maintainer in
	closing bugs. They should only be to fix bugs that have been
	filed in the BTS for at least a week, and generally only when
	the proposed fix has been sent to the maintainer long enough to
	be considered. 

	For NMUs on actively maintained packages, or that fix recently
	filed bugs or bugs with severity normal or below, the maintainer
	should be contacted with the patch before the NMU is uploaded,
	and given enough time (usually a few days) to upload a fix,
	give some indication when a fix will be uploaded, or tell the
	NMUer to go ahead.

	NMUs should be versioned so that the next maintainer upload will
	overwrite them (ie, by bumping the Debian revision by 0.1); and
	the unified diff (diff -ur) between the last maintainer upload
	(or the last NMU) should be sent to the BTS.

	The NMUer should monitor the package's bug page for the next week
	to ensure that the NMU didn't introduce any new bugs. If any new
	bugs were introduced, it's the NMUer's responsibility to fix them.

	NMUers should check the maintainer's entry on db.debian.org for
	any additional notes about the maintainer's availability.