For those of you who receive wp-svn commit emails: I’m considering a simple change to reduce some of the noise on that list. The change would be to not email any commits by bumpbot or potbot.
One of the original goals of bumpbot was to reduce the noise when doing code review on a commit that involved JS JavaScript, a web scripting language typically executed in the browser. Often used for advanced user interfaces and behaviors. or CSS Cascading Style Sheets.. But these commits can occur fairly often and still cause noise.
The concern is two-fold:
- Will skipped commit numbers cause people to look around for them, so instead of saving time, it actually increases time spent on these?
- If a bot screws up and no one is around to hear it, does it make a sound?
I think #1 is surmountable. #2 can be solved in a few ways. One, the commits will still be posted to IRC Internet Relay Chat, a network where users can have conversations online. IRC channels are used widely by open source projects, and by WordPress. The primary WordPress channels are #wordpress and #wordpress-dev, on irc.freenode.net. by svn-bot, and viewable in Trac An open source project by Edgewall Software that serves as a bug tracker and project management tool for WordPress.’s timeline. Two, we could continue to have them sent to a few people, if necessary. Also, these bots have made few mistakes over the years, as every time there’s been a bug A bug is an error or unexpected result. Performance improvements, code optimization, and are considered enhancements, not defects. After feature freeze, only bugs are dealt with, with regressions (adverse changes from the previous version) being the highest priority., we’ve fixed it. Of course, it’s all just VCS, so any issue can be reverted. And we have protection in place around releases to make sure the bots did their jobs and “run clean”.
Anyone have a strong opinion either way?
#bots, #mailing-lists, #svn, #wp-svn