Massive Developers Guide update

[Bill Wohler]

Hey folks,

I just updated the Developers Guide (http://mh-e.sourceforge.net/doc/devguide.html)
to version 2.0 while putting out MH-E 8.5:

* doc/devguide.texi (EDITION): Change to 2.0.
Make changes related to SourceForge 2.0 upgrade. Update name of tools:
Bugs, Feature Requests, Patches, and Support are now under a single
tool called Tickets. Rename the Group field, which spanned both Fixed
In and Found In concepts, to Milestones and now use it to assign a
ticket to a particular release. Update URLs. Change ChangeLog dates to
reflect the change is checked into Emacs. Rename Category to Labels.
Merge Resolution into Status and reduce the number of possible
statuses. Add bzr information for merging changes between trunk and
mh-e branches.

Please have a look at the update to Section 6, Bazaar Repository which
talks about our mh-e branch. I updated the rest of the document to
assume that we do all of our work on that branch.

Next, take a look at the brand-new Section 9, Tickets, which replaces
the previously separate Bugs, Feature Requests, Patches, and Support
sections. It should reflect what we have discussed.

Finally, I revamped Section 10, Releases. It's probably worth a skim so
you know how I use the various tools on SourceForge.

Of note to you includes Section 10.1, Release Schedule which discusses
(in addition to Section 9.3, Milestone) our new use of the Milestone
field which is a far departure of how we used to use the Group field.

You may also find Section 10.4, Release Prerequisites helpful if you
need to merge changes back and forth between the Emacs trunk and mh-e
branches if I'm not around to do so.

Questions, comments, and fixes welcome!

[d.henman]

Bill,
I appreciate you efforts and look forward to using the new version and reading the new developer's manual

Thanks,
Darel