We’ve moved the SVN and Trac firehose mailing…

We’ve moved the SVN and Trac firehose mailing lists to lists.wordpress.org, from the legacy lists.automattic.com. If all goes well, we’ll move the rest of them over as well.

The one side effect is this is likely to break your existing mail filters. The new mailing list emails are wp-trac@lists.wordpress.org and wp-svn@lists.wordpress.org. If you’re using Gmail’s mailing list filters, those would now look like list:wp-trac.lists.wordpress.org.

For those of you who use Gmail, I’ve also added basic styling to the SVN commit emails. Hooray for reading diffs with red and green. (For those who don’t use Gmail, you’ve already been seeing styling that Gmail strips out.)

Just a reminder you don’t *need* to use the Trac firehose. You can also subscribe to individual tickets, milestones, components, focuses, new tickets, etc.

Another note: WordPress.org is now forced SSL. Announcement and details here.

gmail-diffs

#mailing-lists, #notifications, #svn, #trac

For those of you who receive wp svn…

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 or CSS. But these commits can occur fairly often and still cause noise.

The concern is two-fold:

  1. Will skipped commit numbers cause people to look around for them, so instead of saving time, it actually increases time spent on these?
  2. 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 by svn-bot, and viewable in Trac’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, 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