Closed Bug 107310 Opened 24 years ago Closed 23 years ago

create "Image Manager" component assignee: morse, qa: tever. Remove QA from Image Blocking

Categories

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

x86
Windows 2000
task
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: bugzilla, Assigned: ian)

Details

Dont we need a Image Manager component? This component would hold all bugs about (un)blocking images from servers...
For historical purposes, such bugs have been put into the "cookies" component. For no better reason than the fact that the same person implemented both cookie management and image management, and therefore they share common code and are in the same module.
it's just currently I seen block images bugs all around in bugzilla. Some are in imagelib, some in cookies, some in browser generel, some in XPAPPS - UI, etc... I just thought it migth be smart to collect them in one component. Chossing "cookies" as component is not very understandable for the novice mozilla/bugzilla user...:)
I agree completely. My comment above was not saying we shouldn't have a separate component, but rather an explanation of why it wound up in the cookies component.
so was this an ok for a Image Manager component to be created?
Yes it was.
ok, seeking suggestions for descriptions, default assignee (morse?) and qa (HG are you interested)?
sorry I have no time for qa...:(
terri, would you have room on your plate for this?
Seems only right :-)
QA Contact: timeless → tpreston
Seems like tever would be more appropriate only because he is handling cookie-manager q/a and the same code services both.
<q class="OT"><img ID="shrug"> this bug is in a component I qa, i generally like to mark verify when components are created. I had toyed w/ the idea of indicating component and qa ownership using the actual bug about it, but I decided it would be a mess.
Someone want to write up a component description? Is "all bugs about (un)blocking images from servers" sufficient?
Sounds sufficient to me.
See Bug 110363 for a suggestion on an image editor. That bug has been categorized as XP Apps. Should it be set as a duplicate of this bug and it's ideas incorperated and posted here?
no. image manager is unrelated to image editing.
any chance this component could get created? I think there's image manager bugs all over... Image Manager All bugs about (un)blocking images from servers
fixed. component created.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
vrfy fixed
Status: RESOLVED → VERIFIED
Summary: need "Image Manager" component? → create "Image Manager" component assignee: morse, qa: tever
I don't understand what happened here... terri says she can do this in #9, but then tever is assigned QA because morse thinks that tever should qa all his work in #10? Tom never agreed to own QA here, and last I heard, we don't assign "personal" QA to engineers.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
.
Assignee: asa → ian
Status: REOPENED → NEW
QA Contact: tpreston → timeless
what am i supposed to do here?
We already have Image Blocking component. I think this is redundant and can be closed as WONTFIX.
This is the same component, see bug 140169. Ownership needs to be changed from tom anyhow.
I still have no idea what I'm supposed to be doing here. Changing the QA contact? Changing the assignee?
Tom is not going to QA this component. I am trying to see if someone else will take over. If you want to assign this to some placeholder, you can do that right now.
per IRC w/ timeless last night, QA of this should revert to whatever component-placeholder QA you guys want to name it. I'm watching tever's bugmail, so the sooner you do it, the sooner I get relief :)
I have no opinions on the matter. I've changed Image Blocking to have a blank QA. Does that mean it's fixed?
Status: NEW → RESOLVED
Closed: 24 years ago23 years ago
Resolution: --- → FIXED
*shrug*. people should not recycle bugs.
Status: RESOLVED → VERIFIED
Summary: create "Image Manager" component assignee: morse, qa: tever → create "Image Manager" component assignee: morse, qa: tever. Remove QA from Image Blocking
Normally, I'd agree, but this isn't really recycling, this is correcting. The version I heard is that Steve thought he could simply say that because Tom QA'd one thing he worked on, Tom would automatically work on anything else Steve thought was releated. I'm just going to assume he was completely ignorant. But whoever made the initial assignment probably should have checked before creating the component.
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.