> <a href="http://bazaar-vcs.org/IanClatworthy/CoreDeveloperHandbook">http://bazaar-vcs.org/IanClatworthy/CoreDeveloperHandbook</a>.<br><br>That looks good, I'd be happy for you to merge that into the tree whenever you wish.
<br><br><div style="margin-left: 40px;"><span style="font-family: courier new,monospace;">post_commit = bzrlib.plugins.email.post_comm</span><span style="font-family: courier new,monospace;">it</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">post_commit_to = <a href="mailto:bazaar-commits@lists.canonical">bazaar-commits@lists.canonical</a></span><span style="font-family: courier new,monospace;">.com</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;">post_commit_mailer = smtplib</span><br></div><br>Those lines are a good idea but they're not really related to pqm; that's to let other people see your work in progress by sending mail to a list. It's nice but totally optional (if you feel shy about intermediate commits.)
<br><br><blockquote>New features typically require a fair amount of discussion, design and debate. For Bazaar, that information is best captured in a so-called "blueprint" on our Wiki. Overall tracking of blueprints and their status is done using Launchpad's relevant tracker,
<a href="https://blueprints.launchpad.net/bzr/">https://blueprints.launchpad.net/bzr/</a>. Once a blueprint for ready for review, please announce it on the mailing list. (Is that right?)<br></blockquote>That's correct as far as it goes, though we seem recently to have been having those discussions on the list instead, as proposed merges of new developer documents, a situation I think is as good or better.
<br><br>-- <br>Martin<br>