Investigate What Backwards-Compatibility Code Can Be Removed for Bugzilla 3.0

RESOLVED WONTFIX

Status

()

RESOLVED WONTFIX
13 years ago
12 years ago

People

(Reporter: mkanat, Unassigned)

Tracking

({meta})

Details

(Reporter)

Description

13 years ago
There's a lot of backwards-compatibility code for things in various places in Bugzilla, preserving compatibility as far back as 2.8 for some things.

Certain stuff might just be able to go, and we could clean up the code. Of course, some of it we might want to keep. We'll have to investigate what can be removed that's just backwards-compatibility code that we don't need anymore.
(Reporter)

Comment 1

13 years ago
If anybody has any suggestions for things that could be removed, suggest them and we can discuss it here.

Comment 2

13 years ago
How about "Conversion of groups created with ALNC Ticket Ledger versions 2.16 and prior" on editgroups.cgi? Isn't 2.16 going to be debian support only from now on?

Comment 3

13 years ago
(In reply to comment #2)
> How about "Conversion of groups created with ALNC Ticket Ledger versions 2.16
> and prior" on editgroups.cgi? Isn't 2.16 going to be debian support only from
> now on?
> 
If you mean the migration of 2.16 and prior groups, I do not think we should break migration code.  We could, however, get rid of the useentrygroupdefault parameter and the legacy behavior it has.

Comment 4

13 years ago
(In reply to comment #3)
> If you mean the migration of 2.16 and prior groups, I do not think we should
> break migration code.  We could, however, get rid of the useentrygroupdefault
> parameter and the legacy behavior it has.
> 

That is a legacy feature? I just started to use it. It makes life easier when it comes to dividing up a bugzilla installation across many users. Why would you get rid of it? I must be missing something...
(Reporter)

Updated

12 years ago
Group: webtools-security
Target Milestone: Bugzilla 3.0 → Bugzilla 2.24
(Reporter)

Comment 5

12 years ago
Looks like Firefox did some strange selecting of the group radio boxes on the mass-change page when I clicked refresh in my browser before that last mass-change. This is not really a security bug. :-)
Group: webtools-security

Comment 6

12 years ago
WONTFIX per discussion with mkanat on IRC.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → WONTFIX
Target Milestone: Bugzilla 3.0 → ---
You need to log in before you can comment on or make changes to this bug.