Bug 14

Summary: Automatically CC the webteam ML for relevant products / components
Product: Infrastructure Reporter: Samuel Verschelde <stormi-mageia>
Component: BugzillaAssignee: D Morgan <dmorganec>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Normal CC: atelier-bugs
Version: unspecified   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Samuel Verschelde 2011-02-12 01:01:44 CET
Already partially done by rda for the "websites" product (even if mails don't reach the ML for now, problem to be investigated).

Add that automatic CC for the bugzilla component in the infrastructure product too.
Comment 1 D Morgan 2011-02-12 10:02:37 CET
I added mageia-webteam@mageia.org as CC: for bugzilla bugs too.
For the ML i think this is because mageia-webteam@mageia.org need to subscribe to the ML
Comment 2 Samuel Verschelde 2011-02-12 19:52:00 CET
You mean the ML needs to subscribe to itself ?

rda already subscribed bugzilla-daemon@mageia.org to the ML but apparently e-mails never reach there (no bounced mail, no mail waiting for moderation).
D Morgan 2011-02-12 23:31:44 CET

Priority: --- => Normal

Comment 3 D Morgan 2011-02-13 17:45:43 CET
i will investigate.

Btw i have changed and not used CC: but QA Contact, if this doesn't fit your need just tell :)
Comment 4 Samuel Verschelde 2011-02-13 17:54:24 CET
According to bugzilla's help QA contact is not appropriate (rda and me discussed it on IRC and agreed automatic CC is more appropriate than QA contact for now... If the future workflow needs it we can still add QA contacts later)

see http://www.bugzilla.org/docs/2.16/html/programadmin.html :
"The QA Contact should be the person who will ensure these bugs are completely fixed."
Comment 5 D Morgan 2011-02-13 18:31:47 CET
ok for me i fixed this way, i will try to send mails to the ML now
Comment 6 D Morgan 2011-02-14 00:51:02 CET
test
Comment 7 D Morgan 2011-02-14 00:51:55 CET
we can now have webteam as CC: so i close this bugreport.

thanks

Status: NEW => RESOLVED
Resolution: (none) => FIXED