Closed Bug 295936 Opened 19 years ago Closed 10 years ago

Add a NOTMOZ resolution to replace part of what INVALID is currently (somewhat incorrectly) used for. Followup to 295935.

Categories

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

task
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: tristor, Unassigned)

References

Details

(Whiteboard: WONTFIX?)

As I mentioned on bug 295935, were that change to be implemented, it would mean that there would need to be a new resolution created for when a bug was not an issue with a Mozilla product, but /was/ a bug somewhere, and a workaround was not deemed to be needed. I am suggesting that in the spirit of multiple other bug trackers, such as the GNOME and Ubuntu trackers, that we have a NOTMOZ resolution for things that need to be filed elsewhere. In example, if a bug is filed that is present because of a bug in the Sun JRE, and someone files a bug here about it, it needs to be brought to the attention of Sun, but isn't a Mozilla bug, this would then be the correct resolution for it. CCing Asa, same reason as before. Depends on 295935.
Gavin pointed out to me the silliness of having [RFE] in the summary, removed.
Summary: [RFE] Add a NOTMOZ resolution to replace part of what INVALID is currently (somewhat incorrectly) used for. Followup to 295935. → Add a NOTMOZ resolution to replace part of what INVALID is currently (somewhat incorrectly) used for. Followup to 295935.
I concur Bugs that deal with different distros which then backport patches should not be held in the responsibility of the community/devs to hunt down and then find out that they belong to a managed release. If a NOTMOZ resolution was added then anyone in theory that knew the bug being filed was with a particular managed release could kill the bug and freeing more time for development.
(In reply to comment #2) > I concur > > Bugs that deal with different distros which then backport patches should not be > held in the responsibility of the community/devs to hunt down and then find out > that they belong to a managed release. > > If a NOTMOZ resolution was added then anyone in theory that knew the bug being > filed was with a particular managed release could kill the bug and freeing more > time for development. That wasn't exactly what I was thinking of, but nonetheless another example of what this could be used for.
Just so it's clear, there's no *technical* reason we can't do this, because Bugzilla makes it easy to change these now. However, there could be procedural reasons, etc, and it's up to the QA people to decide if they want this or not.
Assignee: justdave → asa
QA Contact: myk → reed
Whiteboard: WONTFIX?
Component: Bugzilla: Other b.m.o Issues → Bugzilla: Keywords & Components
QA Contact: reed → timeless
- This bug is assigned to Asa since 2005 - The default assignee for the current Product/Component is Marcia - But wouldn't an assignment to "nobody" better represent the status of this particular bug?
Assignee: asa → mozillamarcia.knous
Yes. If we ever fix this bug, or something like it, it will be in the context of a review and discussion regarding what resolutions are appropriate for mozilla.org in 2010. Gerv
Assignee: mozillamarcia.knous → nobody
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
while this resolution may help clarify the true state of some bugs, we're putting a freeze on the current statuses and resolutions, due to the impact changing these will have on systems which integrate with bmo (such as dashboards).
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.