Remove OldBugMove extension

RESOLVED FIXED in Bugzilla 6.0

Status

()

Bugzilla
Bug Import/Export & Moving
--
enhancement
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: gerv, Assigned: gerv)

Tracking

({relnote})

4.5.6
Bugzilla 6.0
relnote
Bug Flags:
approval +

Details

(Assignee)

Description

3 years ago
The release notes for Bugzilla 4.0 (released in April 2011) say:

  <li>The system for moving bugs between installations has been
    moved into an extension called <kbd>OldBugMove</kbd>. This system was used
    by very few Bugzilla installations--if you aren't certain
    whether or not you are using it, you're not using it. To enable the system,
    you have to remove the file <kbd>extensions/OldBugMove/disabled</kbd>
    and then run <kbd>checksetup.pl</kbd>. In a future version of Bugzilla,
    this extension may be moved outside of the core Bugzilla code,
    so if you are interested in maintaining it, please let us know.</li>

No-one uses this. Let's kill it. If anyone does want it, they can maintain it themselves.

Gerv

Comment 1

3 years ago
(In reply to Gervase Markham [:gerv] from comment #0)
> No-one uses this. Let's kill it. If anyone does want it, they can maintain
> it themselves.

What do you mean by "let's kill it"? There are tons of extensions that no one uses, except maybe one single installation:

http://git.mozilla.org/?a=project_list;pf=bugzilla


Are you saying moving OldBugMove out of the core code into bugzilla/extensions/ or dropping the code entirely?
Severity: normal → enhancement
OS: Linux → All
Hardware: x86 → All
(Assignee)

Comment 2

3 years ago
Yes, I mean move it out of core. While it's in core, we are responsible for testing it and making it work; I don't think we should be. We can stick it in an extension repo. If someone needs it, they can develop and update it to keep pace. (If it even needs it.)

Gerv
(In reply to Gervase Markham [:gerv] from comment #2)
> Yes, I mean move it out of core. While it's in core, we are responsible for
> testing it and making it work; I don't think we should be. 

100% agreement from me.
(Assignee)

Comment 4

3 years ago
OK, we now have a repo for this:

I can use git subtree to extract the tree and history from the main tree, and then push it to the new repo. We can then remove it from the trunk.

Are we removing it from the 5.0 branch also?

Gerv
(In reply to Gervase Markham [:gerv] from comment #4)
> Are we removing it from the 5.0 branch also?

no, 5.0 branch is for bugfixes only at this point.
(Assignee)

Comment 6

3 years ago
OldBugMove has been extracted to its own git repo here using "git subtree":
http://git.mozilla.org/?p=bugzilla/extensions/OldBugMove.git

Requesting approval to "git rm extensions/OldBugMove" and check in...

Gerv
Flags: approval?

Updated

3 years ago
Assignee: import-export → gerv
Target Milestone: --- → Bugzilla 6.0
Flags: approval? → approval+
Keywords: relnote
(Assignee)

Comment 7

3 years ago
To ssh://gitolite3@git.mozilla.org/bugzilla/bugzilla.git
   47342f0..a427d03  master -> master

Gerv
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.