452757 - Voting help page is out-of-date

Status: RESOLVED FIXED

(Bugzilla :: Documentation, defect)

Description

[Tony Mechelynck [:tonymec]]

On page https://bugzilla.mozilla.org/page.cgi?id=voting.html

Second bulleted list, middle bullet.

There is: [...] the "Vote for this bug" link that appears just above the "Additional Comments" field. [...]

There should be: [...] the "(vote)" link which appears under "Importance" in the bug header.

Comment 2

[Frédéric Buclin]

Attachment: patch, v1

Comment 3

[Frédéric Buclin]

tip:

Checking in template/en/default/pages/voting.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/pages/voting.html.tmpl,v  <--  voting.html.tmpl
new revision: 1.5; previous revision: 1.4
done

3.2rc1:

Checking in template/en/default/pages/voting.html.tmpl;
/cvsroot/mozilla/webtools/bugzilla/template/en/default/pages/voting.html.tmpl,v  <--  voting.html.tmpl
new revision: 1.4.2.1; previous revision: 1.4
done

Comment 4

[Tony Mechelynck [:tonymec]]

The issue that was fixed is not what was reported in comment #0: the latter is not fixed yet. Reopening.

Comment 5

[Reed Loden [:reed]]

This is clearly a Bugzilla issue. Please stop moving this bug out of Bugzilla.

Comment 6

[Tony Mechelynck [:tonymec]]

(In reply to comment #5)
> This is clearly a Bugzilla issue. Please stop moving this bug out of Bugzilla.

There are two issues here. One of them is relative to the Bugzilla package, and in particular to its Voting help page. This issue has been fixed.

BUT... the fix has not (yet) been propagated to the bugzilla.mozilla.org site, whiwh means the problem, *as reported in comment #0*, has not (yet) been fixed. This *propagation* of the fix to whatever Bugzilla software is *installed* at BMO can be regarded as a Bugzilla issue or as a mozilla.org issue. Now that the Bugzilla software is supposedly fixed, I assumed the latter.

Comment 7

[Tony Mechelynck [:tonymec]]

...and, sorry Frédéric, I didn't mean to take this bug off your radar, and a mid-air collistion blocked me from readding you a few minutes ago.

Comment 8

[Frédéric Buclin]

(In reply to comment #6)
> This *propagation* of the fix to whatever Bugzilla software is *installed* at
> BMO can be regarded as a Bugzilla issue or as a mozilla.org issue. Now that the
> Bugzilla software is supposedly fixed, I assumed the latter.

No, things do not work this way. And please let us manage our bugs ourselves. justdave will update bmo in a few days, as he did for the past few weeks, to catch recent checkins made upstream. There is no need to move this bug to say "hey, please update bmo".

Comment 9

[Tony Mechelynck [:tonymec]]

(In reply to comment #8)
> (In reply to comment #6)
> > This *propagation* of the fix to whatever Bugzilla software is *installed* at
> > BMO can be regarded as a Bugzilla issue or as a mozilla.org issue. Now that the
> > Bugzilla software is supposedly fixed, I assumed the latter.
> 
> No, things do not work this way. And please let us manage our bugs ourselves.
> justdave will update bmo in a few days, as he did for the past few weeks, to
> catch recent checkins made upstream. There is no need to move this bug to say
> "hey, please update bmo".

As this bug reporter, donj't I have any say on whether this bug is or isn't fixed? The issue I reported is still there. Therefore it isn't FIXED.

Comment 10

[Reed Loden [:reed]]

(In reply to comment #9)
> As this bug reporter, donj't I have any say on whether this bug is or isn't
> fixed? The issue I reported is still there. Therefore it isn't FIXED.

That's not how things work. When a problem is fixed in the code, the bug is marked fixed. This is exactly how Firefox bugs are handled, too. Not sure why you think Bugzilla bugs should be treated so specially?

Comment 11

[Tony Mechelynck [:tonymec]]

Well, maybe I didn't express myself clearly. I'm trying to be a "good" reporter, and as such I take my QA tasks to heart.

Firefox bugs are marked FIXED when they are fixed-on-trunk; if the bug also affects Thunderbird or SeaMonkey, and the Firefox patch doesn't cure the Thunderbird or SeaMonkey problem, the bug doesn't stay FIXED. So I was trying to understand the relation between the Bugzilla package (as distributed by Mozilla to sites like Novell, Gnome, Mozdev, and others) and the bugzilla.mozilla.org site (including its "local fixes" to Bugzilla). If the relation is parallel to that of Firefox vs. SeaMonkey, then if the "Firefox" fix doesn't apply to a bug originally reported by a "SeaMonkey" user, the bug must be REOPENED and possibly moved (or moved back) from the Core product to the SeaMonkey product. OTOH, if the relation between the Bugzilla software and the BMO site is parallel to that between Minefield (Firefox trunk nightlies) and BonEcho (Firefox 2.0.0.x branch nightlies), then the bug, once fixed on "trunk", can stay FIXED but not VERIFIED, and (unless it is WONTFIX on the "branch"), work on it must still proceed even after the status has been set to RESOLVED FIXED.