246854 - Use Update component for Bugzilla (update.bugzilla.org)

Status: NEW

(Bugzilla :: Extension Ideas, enhancement)

Description

[timeless]

I want to update my bugzilla software, can I use update.mozilla.org to do that?

:)

Comment 1

[Michael Lefevre]

I think this would qualify as an enhancement request.

Comment 2

[alanjstr]

Do you mean you want to download an updated version of Bugzilla through the site?

Comment 3

[Wolf [:wolf]]

Bugzilla's not really an end-user product though. I suppose if it had add-ons
that they probably should/could be hosted with Update. but I'm not seeing how
either smartupdate or the extension/theme hosting that's being done now would
apply to Bugzilla, or any of the Mozilla.org webtools.

Mind you, I see the point.. bugzilla is a mozilla.org product and all. heh.

I'm thinking this is probably a wontfix, since bugzilla tends to do it's own
thing, and has a completely different target market. 

Comment 4

[alanjstr]

I agree that UMO is targetted towards end-users, but I wouldn't completely rule
it out as a place to check for updates to all mozilla.org products.  Any
self-upgrading abilities of webtools would need to be built into them, of course.

Comment 5

[Wolf [:wolf]]

humm.. I suppose this really needs a bugzilla developer's opinion. as to what to
do with it?

CC'ing Dave.

Comment 6

[Dave Miller [:justdave]]

I can't think of any way this would be useful.

Comment 7

[timeless]

i offered one, which was listing contrib bits that are available for a product.
but also just listing the latest versions of the product w/ direct urls to them.
a single point through which to get any product's latest or branch code.

Comment 8

[Dave Miller [:justdave]]

hmm, okay, so this might actually be useful at some point in the not-too-distant
future.

Comment 9

[Dave Miller [:justdave]]

Recent advances in update technology...  :)   the Update software now resides in
mozilla's CVS.  As such, it would be real easy to set up another copy of it and
modify it a bit.  Due to the major difference in target audience, this would be
best done on a separate domain, perhaps update.bugzilla.org.  We could set it up
to serve localization packs, authentication plugins, and so forth.

Comment 10

[alanjstr]

I'm wondering if you really need a separate database.  Perhaps if you can come 
up with a "wishlist" of changes, we can see how they'd mesh with our current 
setup.  I'm certainly for UMO being flexible and extensible, since ideas you 
have for bugzilla may apply to mozilla, too.  Language packs, would be a good 
example.  You could still set up update.bugzilla.org, but share the backend of 
UMO.

Comment 11

[Dave Miller [:justdave]]

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

Comment 12

[Dave Miller [:justdave]]

and per the bug I just duped to this one, themes! :)

Once all the CSSification stuff finishes landing, this would mostly be packs of
css files to go in the "skins" directory

Comment 13

[Ethan Tira-Thompson]

(In reply to comment #12)
> Once all the CSSification stuff finishes landing, this would mostly be packs of
> css files to go in the "skins" directory
I'd like whoever sets this up to keep in mind that a theme might need to consist
of more than just CSS files - I think modification of template files would be
needed as well for contributions of any significance, such as adding icons for
links/buttons, or changing the layout (add a toolbar at the top of the page
instead of the bottom), etc.
Although I realize that defining a "theme" as a template directory would mean
each theme would be language-dependant, which is unfortunate.  I don't know if
there is a good way around that.

Comment 14

[Dave Miller [:justdave]]

Reassigning bugs that I'm not actively working on to the default component owner
in order to try to make some sanity out of my personal buglist.  This doesn't
mean the bug isn't being dealt with, just that I'm not the one doing it.  If you
are dealing with this bug, please assign it to yourself.

Comment 15

[Frédéric Buclin]

justdave, is this feature still wanted? For new releases, we have the notification system since Bugzilla 3.0. Do we want more than that?

Comment 16

[Dave Miller [:justdave]]

(In reply to Frédéric Buclin from comment #15)
> justdave, is this feature still wanted? For new releases, we have the
> notification system since Bugzilla 3.0. Do we want more than that?

Reading the additional comments it sounded like this was intending to keep track of available updates to extensions you're using, rather than Bugzilla itself.  We have enough extensions now that's probably a valid idea now (much moreso than it was in the past).  Something like Drupal 6 and up do where you can load a page that lists all of your installed extensions and whether they're up-to-date or not.