Suggestion: require release name in the approval request Subject line (original) (raw)

Jeff Dinkins jeff.dinkins at oracle.com
Thu Nov 10 20:01:26 UTC 2011

On 08:50 Wed 02 Nov , Dan Smith wrote:

I'd appreciate something like this:

Subject: [7u2 CR] 7099XXX - Duke's nose is the wrong Pantone shade of red

Edvard, Dalibor: what needs to be done to make this official and put into practice?

thanks,

jeff

On Nov 7, 2011, at 3:31 PM, Dr Andrew John Hughes wrote:

On 08:50 Wed 02 Nov , Dan Smith wrote:

I'd appreciate something like this:

Subject: [7u2 CR] 7099XXX - Duke's nose is the wrong Pantone shade of red Right now I've got four different mail rules to try to filter out various review request subject lines; it's very ad hoc. It's nice to separate these messages out, because they're typically much less likely to be of general interest. I like this format better too. (Maybe there are also plans to move these off of the mailing lists entirely as we migrate to JIRA?) Depends how this works out. I wouldn't want to lose any transparency or archiving that the mailing lists provide. A much bigger problem to me at the moment is the amount of commit traffic I get. Can we not have these on a separate list? I need to be signed up to the lists to get the actual patch reviews/discussion, but a commit to tl gives me about five identical e-mails. I understand those on a particular team want to know what's gone in their repository, but surely this could be solved by having corresponding commit lists rather than dumping it all on the discussion list? —Dan -- Andrew :) Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Support Free Java! Contribute to GNU Classpath and IcedTea http://www.gnu.org/software/classpath http://icedtea.classpath.org PGP Key: 248BDC07 (https://keys.indymedia.org/) Fingerprint = EC5A 1F5E C0AD 1D15 8F1F 8F91 3B96 A578 248B DC07

More information about the discuss mailing list