On Saturday 18 September 2010 19:14:27 Brad Roberts wrote: > Emails are on my todo list. My top plans: > > 1) track svn revision id's > > 2) change the build rate to be reactive to submissions (ie, potentially > much faster than once an hour, but also not at all when no changes have > been submitted)
These both sound good. > 3) send breakage emails > > Maybe I should move #3 to be #1. I can add the changes that caused the > brokenness later. Would everyone be ok with receiving one mail every time > anything breaks in any build? Right now that'd mean roughly 2 emails per > hour while things are broken.. potentially 4 per hour when osx/freebsd are > added. That might be a bit excessive. If #2 were done, this wouldn't be a problem, but without it, that could be a bit much. Of course, since it only happens while the things are broken, and it would only be temporary that so many e-mails would be sent, it might be okay. But it also might be better to wait until #2 is done. That's a hard one. I suppose which would be better would depend on how often things are likely to be broken between now and when you get #2 done. If it's daily, that's probably too much. If it's weekly, then it's probably okay. So, I really don't know whether you should wait to do #3 before having done #2. I don't like the idea of the list being flooded with breakage e-mails, but we do want the list to be notified of breakages. > Another thought I had was to have each build cycle contain one and only one > change. If multiple changes come in between runs, still just increment > through them with a couple back-to-back builds. It'd make it a lot easier > to see exactly which change introduced breakage. Also an excellent idea. - Jonathan M Davis _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
