Make it convenient to run the tests with new env vars in sudo
These are more notes for myself than for anyone else's benefit, butI can never remember what all the steps are, so noting them here.Source changes:- Add stanza to NEWS file- Bump setup.py version number- run debchange- Fix the actual problems (updating NEWS, CREDITS, debchange as we go)- Test with dev/chroot-test/run-test- Ensure year in README and doc/manual.docbook is up to date- Update Standards-Version- dev/debian-build/dbuild- CHROOT_TEST_INSTALLDEB=true dev/chroot-test/run-test- When all is well, add release and debian tags- dev/debian-build/dbuild_release- CHROOT_TEST_INSTALLDEB=true dev/chroot-test/run-testPost source changes:- "hg push; hg push public" (also during development)- Mail five files in build/debian to Debian sponsor- Copy orig tarball into ~/hg/lshift-web-personal/personal/paul/mercurial-server/- If need be, overwrite ~/hg/lshift-web-personal/personal/paul/mercurial-server/docbook.html- Pull, update, add, push for lshift-web-personal- Update ~/hg/lshift-web/site/mercurial-server.xml- Push- Test that web page works.- Make a blog post- Post to the mercurial mailing list