653260 - release@m.c email list based on release ldap group?

Status: RESOLVED WONTFIX

(Infrastructure & Operations :: RelOps: General, task)

Description

[Aki Sasaki (not active)]

Two things:

a) is there a single ldap group that controls release@m.c email distribution?
If so, is that the same group that controls who has access to build vpn?

If so, does that mean everyone we add to that group to access loaner machines receives release@m.c email?

b) (unrelated, but related to the filing of this bug) the default assignee and qa contact appears to be broken in bmo.

Comment 1

[Ravi Pina [:ravi]]

Correcting assignee.

Comment 2

[Justin Dow [:jabba]]

a) no, distribution lists are manually maintained outside of ldap, with the exception of certain HR related lists like mv-all@, contractors@, employees@, etc. Furthermore, I think there are about three different ldap bits that Releng employees get, of which only one is used for the build-vpn and I'm not aware of anything else that uses that bit.

CC'ing jlazaro to correct me if I'm wrong about that.

for b), I'm changing summary and assigning to justdave to see what might be broken about the default assignee and qa contact. What was it set to vs. what it was supposed to be set to?

Comment 3

[Reed Loden [:reed]]

b) is being handled elsewhere.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

(bug 653269)