Closed Bug 213919 Opened 21 years ago Closed 17 years ago

Thunderbird components and qa contacts

Categories

(bugzilla.mozilla.org :: Administration, task)

Other
Other
task
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: timeless, Assigned: ian)

References

Details

Now that the first round is done, let's consider what you left out.

components for:
l10n/i18n
filter/junk
security/privacy
filehandling/extensions
os integration
help
general

i'd like something for backend stuff even as a temporary placeholder so that
someone else can later move them to another product. its description could even
explain which other products can get thunderbird bugs and under what conditions.

Again it'd be nice if placeholder QAs were used for individual components so
that people who  only care about individual components can ignore the rest.

The list of components I'm suggesting are based on bugs evicted from MailNews
and my knowledge of the other products (e.g. Camino).
I don't really understand what I'm supposed to do here, but I imagine it'll all 
be taken care of when we do the big reorg.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WONTFIX
it isn't. this is a followup
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
that's great but unless you say what you want in clear english you ain't gonna 
get it.
right then.
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → INVALID
what you're supposed to do:
create a component for each of the lines listed after 'components for:' in
comment 0.

you can use the default assignees for thunderbird. component descriptions can be
stolen from camino
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
one addendum from bug 215841 a "Build" component. Assignee could possibly be
Bryner (or nobody).
*** Bug 216011 has been marked as a duplicate of this bug. ***
Is this likely to be fixed soon, or should I just file my build bugs under some
other random component?
*** Bug 216011 has been marked as a duplicate of this bug. ***
The majority of the proposed components are not Thunderbird-specific but would 
go into the backend product as per the reorg plan. Since there doesn't appear to 
be any demand for this other than from timeless, this is going to be WONTFIX 
unless I hear from someone other than timeless saying that they need something 
done here.

In particular: Scott: Let me (Hixie) know on IRC if you need any components for 
your product, and I'll file the relevant bugs and do the relevant work for you.
Status: REOPENED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → WONTFIX
There are at least two components for "thunderbird" which are very likely
needed:
1. "Build config" for buildsystem specific issues (since there are already a
couple of open thunderbird-specific build issues and there will likely be some
in the future)
  and
2. "Other" - for bugs which do not fix into the existing categories
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
re: comment 11
build config has been added; see bug 216011 (thanks Iain)
Will be done as part of ongoing reorg.
Status: REOPENED → ASSIGNED
*** Bug 228217 has been marked as a duplicate of this bug. ***
Re: comment#10 "The majority of the proposed components are not
hunderbird-specific but would go into the backend product as per the reorg plan."

For those of us who are not in the inner circle, and know nothing of the reorg
plan, ignoring this would be pretty unhelpful.
(In reply to comment #16)
> Plan: http://www.damowmow.com/playground/bugzilla-plan.txt

Any estimate when will Thunderbird will have all the components like mailnews?
This but is open for 14 months.
What's left to do here, timeless? I think the Tbird components we have now are
actually pretty reasonable. 
Seems to be done. Open a new bug for new issues.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago17 years ago
Resolution: --- → FIXED
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.