It would be nice if you could add some extra possible values to the "Version" field. I would suggest adding: - A "CVS image" with an extra field for the date/time of the last "cvs update" - An extra text field for the "Other" choice - An "Unknown" (with no extra fields).

The database is being reorganized a bit. Instead of the Bugzilla product, a new Webtools product has been created, with Bugzilla being a component of it. This bug is being moved from the old Bugzilla product to the new Webtools product.

Reassigning to dmose@mozilla.org, who now has front-line responsibility for all Bonsai and Bugzilla bugs.

Reassigning back to me. That stuff about me no longer being the front-line person responsible for Bugzilla and Bonsai turned out to be short-lived. Please pardon our confusion, and I'm very sorry about the spam.

It seems Bugzilla does now have an "Other" option... Should this bug be marked as FIXED?

No; the request was to add free-text input when "other" is selected.

tara@tequilarista.org is the new owner of Bugzilla and Bonsai. (For details, see my posting in netscape.public.mozilla.webtools, news://news.mozilla.org/38F5D90D.F40E8C1A%40geocast.com .)

marking this as won't fix. here's my thinking on it: 1) It's really easy for a Bugzilla administrator to create a version number. When this bug was originally created, we didn't have the HTML forms for adding and removing products with associated version numbers. 2) letting individual users control which version they report a bug against scares the living daylights out of me. there's too much room for a user to make an error. this way it forces the user to look for a valid version number and if not, use other. all unaccounted for bugs with unaccounted versions drops into the 'other' bucket, instead of the various other buckets of 'i can't type', 'i couldn't find my version number, so i'm going to create a random one', or my favorite 'i'm going to recreate version 1.0 even through it's staring me right in the face'.

I might be inclined to verify this and close off my similar/dupe bug #38520, but first I'd like to know why mozilla.org is not using the version field at all and see if there are any deficiencies we can identify. Dawn? Obviously including every nightly is impractical for a list box, but what's wrong with M17, M18, 0.6, 0.8, nightly build, other?

ping -f endico.mozilla.org

ping endico... Matty wants you to verify... see previous comments on this bug.

marking verified because the possible values of the version field should be limited to a pre-determined set, not the infinite number of goshknowswhat that end-users would type in. There's no particular reason why the Mozilla product doesn't use the version field. On the occasions when we've discussed it we couldn't agree on what the versions should be and there wasn't enough of a demand to use the field to bother resolving the issue.

moving to Bugzilla product reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE