Last modified: 2011-01-25 01:02:18 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T18777, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 16777 - Upgrade Bugzilla to 3.4
Upgrade Bugzilla to 3.4
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Fred Vassard
: shell
: 22030 (view as bug list)
Depends on: 22159
Blocks: 148 1463 9025 17514
  Show dependency treegraph
Reported: 2008-12-23 23:40 UTC by Sam Reed (reedy)
Modified: 2011-01-25 01:02 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Sam Reed (reedy) 2008-12-23 23:40:02 UTC
Was released in late november...

Suspecct it might be worth upgrading to take advantage of any/all new features?
Comment 1 Siebrand Mazeland 2009-02-10 01:16:57 UTC
Release of Bugzilla 3.2.2, 3.0.8, and 3.3.3 [ 2009 Feb 03 ]. Contains security fixes. Raised priority.
Comment 2 Brion Vibber 2009-03-27 22:31:56 UTC
Note that Tim did the 3.0.8 security upgrade in February.

We'll be wanting to peek at 3.2 or 3.3 at some point; will probably want to evaluate the upgraded on a copy, see what new features/workflow stuff we can benefit from, and see what we want to do about the theme.

(Honestly, maintaining the Monobook-style theme is a big pain in the butt. We'll probably want to have a less thorough 'theme conversion' that maintains a general 'Wikimedia look & feel' without doing all the restructuring that makes fixing theme templates on every ugprade so tedious.)
Comment 3 Brion Vibber 2009-03-30 21:26:15 UTC
Comment 4 Rob Halsell 2009-06-01 15:57:25 UTC
Bugzilla currently resides on Isidore.  However, upgrading it here is useless, as it needs to move to Singer.  Just FYI that you could just save time by doing the install on Singer.
Comment 5 Fred Vassard 2009-06-03 16:21:46 UTC
Current bugzilla version now installed on Singer. The skin has been ported, and so have the cronjobs.
It is currently running out of a copy of the current bugzilla database (last update from Monday June 1st): bugzilla_testing.
I will reserve a couple of days for testing before taking it live.
It is currently running on

Let me know if you see anything weird. 

Comment 6 Brion Vibber 2009-07-27 16:25:01 UTC
Bumping update req to 3.4 which has some niceties...

For the skin, I recommend that rather than attempting to port the Monobook skin again, we make a more modest theme that fits visually nicely with the new Vector skin but avoids the HTML restructuring that has made maintenance of the Monobook theme across BZ upgrades a big pain in the butt. Talked w/ Trevor a little about that at OSCON last week, will add a dep on him. :)
Comment 7 Fred Vassard 2009-07-27 16:29:17 UTC
Awesome! I will resinstall (I was trying to port the old skin, but it is a pain) a stock version of the latest and greatest from Bugzilla (which will be on singer (with a convenient cname of bugzilla3.w.o).

Trevor, I will let you know as soon as it is ready for "customization"! 

Comment 8 Fred Vassard 2009-09-10 22:41:20 UTC
test edit -ignore-
Comment 9 Sam Reed (reedy) 2009-10-02 17:55:11 UTC
IRC cabal say just upgrade ;D
Comment 10 Sam Reed (reedy) 2009-11-11 21:17:55 UTC
"All users are recommended to use Bugzilla 3.4.3 instead, and users of Bugzilla 3.0 are encouraged to upgrade to 3.4.3 as soon as possible."


Seems we're on 3.0.8 according to the front page, 3.0.10 is highest security version in that branch
Comment 11 Sam Reed (reedy) 2010-01-06 09:24:13 UTC
*** Bug 22030 has been marked as a duplicate of this bug. ***
Comment 12 Fred Vassard 2010-01-19 20:32:01 UTC
Bugzilla has been upgraded to 3.4.4. 
Resolving this long standing "bug"!

Note You need to log in before you can comment on or make changes to this bug.