292026 - move Firefox:Software Update to Toolkit:Application Update

Status: RESOLVED FIXED

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

Description

[Darin Fisher]

I think we should have a toolkit component for software update.

  Toolkit: Update System
  Default Assignee: [e-mail]
  Default QA: [e-mail]

Sound good?

Comment 1

[Darin Fisher]

Hrm.. it looks like 'Firefox: Software Update' is actually being used for
Deerpark software update bugs.  I guess we don't really need a toolkit bug
component then... though much of software update could apply to thunderbird or
other toolkit based apps.

Comment 2

[timeless]

if software update belongs in toolkit, i'd rather ask that it be moved.

Comment 3

[Darin Fisher]

timeless: it's hard to say... perhaps there are UI elements of software update
that are firefox specific?  most of the code is generic.  so, we could move the
component from firefox, but then we might end up wanting a component in firefox
again for firefox specific UI issues related to software update.  maybe that's
the better approach as it will reduce the number of bugs that need to be
shuffled around most likely.

Comment 4

[Reed Loden [:reed]]

marcia is now the default assignee for Bugzilla: Keywords & Components.

Comment 5

[Ben Turner (not reading bugmail, use the needinfo flag!)]

*** Bug 328506 has been marked as a duplicate of this bug. ***

Comment 6

[Ben Turner (not reading bugmail, use the needinfo flag!)]

(In reply to comment #3)
> timeless: it's hard to say... perhaps there are UI elements of software update
> that are firefox specific?  most of the code is generic.  so, we could move the
> component from firefox, but then we might end up wanting a component in firefox
> again for firefox specific UI issues related to software update.  maybe that's
> the better approach as it will reduce the number of bugs that need to be
> shuffled around most likely.

I completely agree. Product-specific problems certainly exist, but the majority of the bugs I've seen have implications across products.

Comment 7

[Marcia Knous [:marcia]]

Need some clarity here as to what we want done.

Comment 8

[Benjamin Smedberg]

Marcia, the "Firefox: Software Update" component should become "Toolkit: Software Update".

Comment 9

[Ben Turner (not reading bugmail, use the needinfo flag!)]

I still think comment 3 is the right way to go...

Turn all the "Firefox: Software Update" bugs into "Toolkit: Software Update" bugs, keep "Firefox: Software Update" as a valid component, then we can go in and move the Firefox-UI-specific bugs back to "Firefox: Software Update".

Is that reasonable?

Comment 10

[Benjamin Smedberg]

It's unnecessary: a multitude of bugzilla components doesn't really help anyone. The single toolkit component should be sufficient.

Comment 11

[Ben Turner (not reading bugmail, use the needinfo flag!)]

Sounds good.

Comment 12

[Steffen Wilberg]

Resummarizing per comment 8.

Comment 13

[Phil Ringnalda (:philor)]

Marcia: can we please do this, then, since it's what the submodule owner originally wanted, when he filed the bug, and what the module owner has said is the right thing a couple of times now, and the only objection doesn't hold since Firefox's UI is nothing but strings for a menuitem? Right now, Thunderbird is using Tb: General, Tb: Installer, Tb: Build Config, and probably Tb: Preferences as random spots to abandon update bugs, since apparently nobody wants to move Thunderbird bugs to the Firefox product.

Comment 14

[Phil Ringnalda (:philor)]

Oh, I missed seeing the stalled bug 271978 that's a superset of this.

Comment 15

[Mark Banner (:standard8)]

Isn't this fixed now? (with the bugzilla reorg) We now have Toolkit: Application Update...

Comment 16

[Steffen Wilberg]

Indeed, fixed as part of the BMO reorg in July 2008, http://www.gerv.net/temp/bmo-reorg.html.