Bug 20556 (bugzilla50) - Upgrade bugs.mageia.org to Bugzilla 5.0.3
Summary: Upgrade bugs.mageia.org to Bugzilla 5.0.3
Status: RESOLVED FIXED
Alias: bugzilla50
Product: Infrastructure
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Frédéric "LpSolit" Buclin
QA Contact:
URL: http://gitweb.mageia.org/web/bugs
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-22 22:43 CET by Frédéric "LpSolit" Buclin
Modified: 2017-04-14 22:39 CEST (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Frédéric "LpSolit" Buclin 2017-03-22 22:43:42 CET 
Per the thread on https://ml.mageia.org/l/arc/sysadmin-discuss/2017-03/msg00031.html, the plan is to upgrade bugs.mageia.org to 5.0.3 using this branch: http://gitweb.mageia.org/web/bugs

I will manage the upgrade. Mageia-specific customizations will go into the Mageia extension as much as possible to make future upgrades easier:

http://gitweb.mageia.org/web/bugs/tree/extensions/Mageia
Comment 1 Nicolas Lécureuil 2017-03-23 18:15:46 CET 
We need to achieve this great task.

to have a good test i think we should create a bugzilla-dev module and work on it ( and use it on sucuk ) and when ready we should git copy bugzilla-dev into bugzilla.

This will allow to test and use a new database ( a copy of the existing one ).


What do you think of this first step ?

CC: (none) => mageia

Comment 2 Frédéric "LpSolit" Buclin 2017-03-23 20:18:40 CET 
As I understand it, there is nothing I can do at this point. The code is in git for almost a year, and puppet will manage git pulls.
Comment 3 Nicolas Lécureuil 2017-03-23 21:13:07 CET 
can someone copy bugs database into bugs-dev ?
Nicolas Lécureuil 2017-03-25 23:49:39 CET

CC: (none) => mageia, pterjan, tmb

Comment 4 Nicolas Lécureuil 2017-04-08 14:56:07 CEST 
should be OK Frédéric

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.