232065 - Clean up default OS list

Status: RESOLVED WORKSFORME

(Bugzilla :: Bugzilla-General, defect)

Description

[Gervase Markham [:gerv]]

At a minimum, we should remove:

        "Windows 3.1",
        "Mac System 7",
        "Mac System 7.5",
        "Mac System 7.6.1",
        "Mac System 8.0",

and add:

        "Windows Server 2003",
        "Mac OS X 10.3"

Other candidates for removal, based on the existence of an "other" category, the
small number of bugs on b.m.o., and the ability for other Bugzilla sites to add
things to the list anyway:

        "BSDI", (3)
        "Mac System 8.5", (22)
        "Mac System 8.6", (6)
        "NetBSD", (7)
        "OpenBSD", (7)
        "Neutrino", (10)
        "OpenVMS", (11)
        "IRIX", (15)

We probably shouldn't remove any OS where the OS vendor ships our stuff, no
matter how few bugs there are. That means we need to keep OpenVMS and Irix. I
don't know whether the two BSDs ship us.

The platform list is probably OK.

We'd need to change the OS sniffing code to be smarter; if it sniffed an OS
which wasn't in the currently-available list, it would return "other".

Gerv

Comment 1

[Wolfram Schlich]

Is there a way to *easily* "patch" the list myself? Or documentation on how to
do it, if it's not so easy? :-) We're using Bugzilla for our QA and we need
"Windows Server 2003" in the OS list.

Comment 2

[Gervase Markham [:gerv]]

Yes - just edit localconfig and rerun checksetup.pl.

Gerv

Comment 3

[Gervase Markham [:gerv]]

Dave: we have a bit of a problem here, don't we? If we alter the list, and
change enter_bug.cgi to match, then installations which have the old list but
get the new enter_bug.cgi will have mismatches all over the place.

For example, if we replace all the pre-OS X Mac versions with "Mac OS 8/9", and
the sniffer code starts returning that value, then people without it in their
lists will have problems...

Gerv

Comment 4

[Dave Miller [:justdave]]

Hmm, yes.  Once this is in the database and not in localconfig, this would be a
bit easier.

My prefered way of handling this would be to have the sniffing code be really
really specific to the point of being anal. :)

Then in the page where the admin can edit the OSes and platforms and so forth,
we allow them to match multiple return values from the sniffing code to each
entry in their list.  The defaults would of course be sane. :)

Comment 5

[Gervase Markham [:gerv]]

Dave: that sounds somewhat complicated... It would also make it harder for
people to do the common trick of co-opting these fields for something else.

This needs more thinking about...

Gerv

Comment 6

[Dave Miller [:justdave]]

well, if we get custom fields in, then people won't have to co-opt it :)

Comment 7

[Gervase Markham [:gerv]]

Dave: this problem happens in reverse too. We've added new values, and new
sniffing code - but if people upgrade, their enums won't have the new values,
and things will break. Won't they? Hmm. I guess maybe just the default will get
selected instead...

Gerv

Comment 8

[Frédéric Buclin]

The list has already been cleaned up as part of bug 17453 1.5 year ago.