one can create a Firefox bug but the 3.0 branch is not available as a version

RESOLVED WONTFIX

Status

()

bugzilla.mozilla.org
Administration
RESOLVED WONTFIX
10 years ago
7 years ago

People

(Reporter: Ray Kiddy, Assigned: marcia)

Tracking

Details

(Reporter)

Description

10 years ago
MoCo is releasing early versions of Firefox 3.0. Why must one still file a bug with Version == "Trunk"? It does not seem very accurate.

Comment 1

10 years ago
we haven't branched for 3.0, there's no alternative to 3.0.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

10 years ago
The version for the product in bugzilla should only follow the cvs tags? Why? When one goes to the version string for one of the nightly build. It does not say "Trunk". Why would it? It says 3.0b5pre. This is a version number, yes?

So, when one reports a bug, should this not be the version number for the product as specified in bugzilla?
Status: RESOLVED → REOPENED
Resolution: INVALID → ---

Comment 3

10 years ago
Bugzilla's version field tracks the branches.. not the milestones. The 3.0alpha and beta releases are simply snapshots of the head, trunk code. Since a bug will appear on a specific branch until its fixed there, filing a bug against a specific version is less useful. Its perfectly accurate. The guided form will also provide automatically the user agent you're filing from, which includes the build ID in the user agent string.
We're not adding 3.0 until we've released (and have moved on to Hg as the "Trunk"). WONTFIX for now. Feel free to reopen once we've moved completely to Hg.
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago10 years ago
OS: Mac OS X → All
Hardware: PC → All
Resolution: --- → WONTFIX
(Reporter)

Comment 5

10 years ago
Ok, but I think this is a mistake. You are using internally valid logic. But when a user outside of MoCo is filing a bug on the browser, given the version information visible to them, they should not have to translate externally obvious logic (version = "3.05bpre") to internal logic (version = "Trunk").

Now, when one files a bug against a Core component, then internal logic makes sense.

But when filing a bug against Firefox, the external logic should determine the version of Firefox that the bug is filed against.

MoCo keeps saying they want more people to participate. I believe them. So, everybody filing a bug needs to adopt the logic internal to MoCo?
(In reply to comment #5)
> MoCo keeps saying they want more people to participate. I believe them. So,
> everybody filing a bug needs to adopt the logic internal to MoCo?

This bug has nothing to do with "MoCo". Bugzilla version fields and associated common practices existed long before MoCo did.

The majority of end-users end up filing bugs using the guided bug form, which doesn't require you to choose a version.
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.