Closed Bug 2497 Opened 26 years ago Closed 26 years ago

Need to set up bugzilla fields to include mail/news area

Categories

(Bugzilla :: Bugzilla-General, defect, P2)

defect

Tracking

()

VERIFIED FIXED
Bugzilla old

People

(Reporter: lchiang, Assigned: terry)

Details

Need to set up bugzilla fields to include mail/news area Soon, we will have some mail/news code available and we need to have the bug infrastructure set up to support this. In looking at the bugzilla page where various products/projects are listed, I don't see a product/project name where the bug filer can easily recognize that s/he can enter mail/news bugs there. Here is what we'd like, if possible: (1) Have a product/project named "mail/news" with components tbd. All other fields (ie. priority, platform, etc) should be the same as the NGLayout project. OR (2) Include a "mail/news" component in an existing project/product, but that would involve renaming the project/product to be more informative that mail/news bugs can be filed there. What is your opinion, Terry? (Or whomever this bug report gets filed against). Thanks.
You will need to provide terry with a description of the Mail/News product before he can enter it.
I believe the description should read: "For bugs about the Mozilla Mail/News Project" with a link to: http://www.mozilla.org/mailnews/index.html which is a description of the Netscape branded mail/news effort.
Status: NEW → ASSIGNED
I agree it probably makes sense for mail/news to be its own project. (I'll probably name it "MailNews", if that doesn't bother anyone too much.) But I really need a list of components for it. And for each component, I need a default owner -- someone who will initially get assigned bugs submitted against that component. So, generate me an initial list of components and owners, and I will create an area in Bugzilla for you.
MailNews sounds fine. Here are some component suggestions. I'll email these around to make sure everyone agrees, and add their suggestions/corrections. Networking - Scott MacGregor <mscott@netscape.com> Database - David McCusker <davidmc@netscape.com> MIME - Rich Pizzarro <rhp@netscape.com> Security - Jeff Tsai <jefft@netscape.com> Composition - Jean-Francois Ducarroz <ducarroz@netscape.com> Address Book - Scott Putterman <putterman@netscape.com> Front End - Warren Harris <warren@netscape.com> Back End - Phil Peterson <phil@netscape.com>
Great. Just be sure to let me know when you think the dust has settled (even if that translates to "just do the above".)
Thank you, Terry. Does it make sense to have "security" as a component? I thought that security was one area that we could not include on mozilla.org.
Security bugs are NOT to go into Bugzilla. Must be tracked separately in Bugsplat. chofmann - this still the way to go here?
Security bugs are NOT to go into Bugzilla. Must be tracked separately in Bugsplat. chofmann - this still the way to go here?
Phil, did you get any agreements or additions to your suggested list?
No one suggested changes. Let's go with this, and amend it if/when we have problems.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
OK, done.
Status: RESOLVED → VERIFIED
Verified as done. Thanks terry!
Moving to Bugzilla product
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
QA Contact: matty
Target Milestone: --- → Bugzilla old
Version: other → unspecified
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.