Core Developer Handbook draft

[Martin Pool]

> http://bazaar-vcs.org/IanClatworthy/CoreDeveloperHandbook.

That looks good, I'd be happy for you to merge that into the tree whenever
you wish.

post_commit = bzrlib.plugins.email.post_commit
post_commit_to = bazaar-commits at lists.canonical.com
post_commit_mailer = smtplib

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.)

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,
https://blueprints.launchpad.net/bzr/. Once a blueprint for ready for
review, please announce it on the mailing list. (Is that right?)

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.

-- 
Martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20070618/743a9ee3/attachment.htm