Bug 55882 - Upgrade bugs.webkit.org to latest Bugzilla 5.0.3
Summary: Upgrade bugs.webkit.org to latest Bugzilla 5.0.3
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit Website (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: David Kilzer (:ddkilzer)
URL: http://trac.webkit.org/wiki/UpdatingB...
Keywords: InRadar
: 82632 167052 (view as bug list)
Depends on: 115667
Blocks: 57200
  Show dependency treegraph
 
Reported: 2011-03-07 09:25 PST by Frédéric Buclin
Modified: 2017-03-22 10:19 PDT (History)
11 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric Buclin 2011-03-07 09:25:37 PST
https://bugs.webkit.org/ is currently running Bugzilla 3.2.3, which reached EOL last month. You should upgrade to 4.0.
Comment 1 David Kilzer (:ddkilzer) 2011-03-13 09:47:19 PDT
Some notes for anyone looking into this:

Bugzilla on bugs.webkit.org has a number of local modifications (which aren't always identified by comments) that must be merged into a new version and then qualified in a test environment before being deployed.  The custom templates are the most difficult to merge because they're not modified in place, so the changes have to be reapplied to new copies of the updated templates.

Many of the local modifications should have bugs (enhancement requests) filed on <https://bugzilla.mozilla.org/> so that we can eventually get out of the business of local modifications to make upgrades easier.

There are some notes here on how to upgrade, but it may be easier to take a diff of the changes against 3.2.3 and then apply them to 4.0:  <http://trac.webkit.org/wiki/UpdatingBugzilla>.

After it's deployed, there is usually fallout from the UI changing in the form of complaints, and you'll rarely get any accolades for finishing the update.  (Just something to look forward to. :)
Comment 2 Frédéric Buclin 2011-06-15 10:23:31 PDT
Would you agree to attach a diff of the bugs.webkit.org code vs vanilla Bugzilla 3.2.3? I'm wondering how much code could be moved into an extension (which would save you a lot of trouble every time you want to upgrade).
Comment 3 Frédéric Buclin 2012-02-25 14:21:57 PST
Bugzilla 4.2 has been released this week. It has many security improvements compared to 3.x.
Comment 4 Eric Seidel (no email) 2012-03-28 15:34:41 PDT
How would someone who doesn't work at Apple attempt such an upgrade?  It seems we'd need access to the server?  (This bug came up again today in discussing why webkit-patch is so slow... one of the reasons being it talks to bugzilla via page scraping.)
Comment 5 David Kilzer (:ddkilzer) 2012-04-19 09:17:54 PDT
(In reply to comment #4)
> How would someone who doesn't work at Apple attempt such an upgrade?  It seems we'd need access to the server?  (This bug came up again today in discussing why webkit-patch is so slow... one of the reasons being it talks to bugzilla via page scraping.)

The bulk of the work is doing the merge and cleaning up conflicts, then fixing any issues that occurred as a result of the merge.  You could perform the merge, set up a test server, and then make sure basic functionality works, then commit the changes to a branch or generate a patch.

Having said that, I'm going to attempt to upgrade Bugzilla during the WebKit Contributors Meeting.
Comment 6 David Kilzer (:ddkilzer) 2012-04-23 16:21:13 PDT
(In reply to comment #5)
> Having said that, I'm going to attempt to upgrade Bugzilla during the WebKit Contributors Meeting.

Status update:  I've merged the changes up to v4.2.1, but I need to shake out merge issues on a test instance of Bugzilla.  Due to various scheduling issues, I won't be able to work on this for a couple of weeks.  Will get back to it as soon as possible.
Comment 7 Eric Seidel (no email) 2012-04-23 16:34:40 PDT
Fantastic!  Thank you for looking at this Dave!
Comment 8 Eric Seidel (no email) 2012-08-02 15:07:03 PDT
*** Bug 82632 has been marked as a duplicate of this bug. ***
Comment 9 David Kilzer (:ddkilzer) 2013-05-02 15:03:00 PDT
Working on this now at the WebKit Contributors Meeting.
Comment 10 Frédéric Buclin 2013-05-30 09:19:18 PDT
Bugzilla 4.4 has been upgraded meanwhile.
Comment 11 Frédéric Buclin 2013-11-02 10:24:46 PDT
And 4.4.1 includes several security fixes.

Any progress since your last comment 9?
Comment 12 Csaba Osztrogonác 2016-01-08 01:04:46 PST
As far as I know, we still use 4.2.11. 

4.2.16 is the latest and the last relase of 4.2.x
since 4.2.x reached of its EOL on 2015 Dec 22:
https://www.bugzilla.org/news/
Comment 13 Csaba Osztrogonác 2016-01-29 04:38:43 PST
Any interest to upgrade bugzilla to a still supported version?
Comment 14 David Kilzer (:ddkilzer) 2017-03-21 12:14:44 PDT
Testing upgrade of Bugzilla 5.0.3.
Comment 15 David Kilzer (:ddkilzer) 2017-03-22 10:17:51 PDT
<rdar://problem/22524280>
Comment 16 David Kilzer (:ddkilzer) 2017-03-22 10:18:53 PDT
*** Bug 167052 has been marked as a duplicate of this bug. ***
Comment 17 David Kilzer (:ddkilzer) 2017-03-22 10:19:45 PDT
Bugzilla has been upgraded to version 5.0.3.