Bugzilla

 - I've added support for waiting until N new commits have occured and then further support for waiting to satisfy both at least N weeks since the last job and M new commits
 - I've excluded merge commits from the count of commits and the bug description
 - Changing the commit message (to add the word 'version') is actually more trouble than it seems because the [verification script](https://searchfox.org/mozilla-central/source/taskcluster/scripts/misc/verify-updatebot.py) has t be able to parse it; and landing an updatebot bump and the verification script is a flag day type thing - I figured not having 'version' isn't that big a deal?
 - Instead of `npm install / gulp mozcentral` is there an argument to omit the download of FF Nightly and tests run on it as part of the build process?

But I think we're pretty close.

 - I've added support for waiting until N new commits have occured and then further support for waiting to satisfy both at least N weeks since the last job and M new commits
 - I've excluded merge commits from the count of commits and the bug description
 - Changing the commit message (to add the word 'version') is actually more trouble than it seems because the [verification script](https://searchfox.org/mozilla-central/source/taskcluster/scripts/misc/verify-updatebot.py) has t be able to parse it; and landing an updatebot bump and the verification script is a flag day type thing - I figured not having 'version' isn't that big a deal?
 - Instead of `npm install / gulp mozcentral` is there an argument to omit the download of FF Nightly and tests run on it during the vendoring process, so they can just run during PR merging?

But I think we're pretty close.