https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7620
Bug ID: 7620
Summary: Proposed change to release process document
Product: Spamassassin
Version: 3.4 SVN branch
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Building & Packaging
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: Undefined
After seeing the number of reply-alls to the announcement message for the
release of 3.4.2, I propose that we change the step in build/README to specify
that the announcement be sent in some way that would not have a reply-all go to
all the lists that the announcement is sent to.
I can think so far of three possible ways to so that. I'm proposing that the
README specify exactly one procedure that we decide on here, so that the README
leaves no ambiguity for the step.
Three examples that would accomplish this are: 1) Send separate emails, one to
each mailing list address (more work for the release manager); 2) Send it To
the announce list (since reply-all will always end up moderated anyway) with
Bcc to the other lists (so ordinary reply to the list will work, but reply-all
will not have the negative effect); 3) Send it To some dummy or no-reply
address that we come up with, with Bcc to all the lists
I would like to come to a consensus on how to do this and the make the change
in the README.
--
You are receiving this mail because:
You are the assignee for the bug.
