Policy for grafting bug fixes from dev to stable

[Rik]

jwe,

How do we want to handle bug fixes (not addition of new features) which
were made on the development branch because the stable branch was in a code
freeze during the release process?  Some of the patches fix legitimate
bugs, but there was insufficient time for testing the patches so the code
went to the dev branch.  One strategy is to assume that there are enough
testers on the development branch so that by the time the 5.2.0 bug fix
release is made in, say 4 months, there has been sufficient vetting of the
patches.  In that case, a suitably complex hg expression that extracts
csets from the date when stable and dev diverged to the present, which were
made on the development branch, and which reference "bug #" should produce
an initial list for grafting back to stable.  The list would still need to
be pared of bugs which were actually new feature additions.

--Rik