1079136 - Category of the bug is marked as Unresolved while it is fixed

Status: RESOLVED WONTFIX

(Websites :: Nucleus, defect, P1)

Description

[Sylvestre Ledru [:Sylvestre]]

Reported initially in bug 237623

On:
https://www.mozilla.org/en-US/firefox/33.0a2/auroranotes/
the category of "Fix incomplete downloads being marked as complete by detecting broken HTTP1.1 transfers (237623)" is Fixed

On:
https://www.mozilla.org/en-US/firefox/33.0beta/releasenotes/
the note in the category "Known issues" and the category is unresolved (while we can see "Resolved in v33.0a2")

We have the same issue with the 33.0 release notes https://www-dev.allizom.org/en-US/firefox/33.0/releasenotes/

It is the same item in the nucleus db.
"Fixed in release:" is v33.0a2 and the selected version are all 33.0 version.

I see a few potential fix:
* Manage this in bedrock. If a version is selected, it should be marked as Fixed (even when "Fixed in release" is different)

* Workaround: Move the "Fix in release" to the 33.0 release (the one which matters at the end)
* Workaround: Only put the note for the release itself

Comment 1

[Marc Bejarano]

the effect of this bug is now showing to a wide audience.  i'm using the release version of firefox and was just prompted to update to 33.0.  for some reason, the release notes link offered takes me to https://www.mozilla.org/en-US/firefox/33.0beta/releasenotes/ which exhibits this bug.

Comment 2

[Josh Mize [:jgmize]]

(In reply to Sylvestre Ledru [:sylvestre] from comment #0)
> I see a few potential fix:
> * Manage this in bedrock. If a version is selected, it should be marked as
> Fixed (even when "Fixed in release" is different)

I think this would not give the desired results in all cases, but if we add some logic that takes the ordering of releases into account, (33.0 > 33.0b1 > 33.0a2) we could automatically display "fixed" for the correct versions.

> * Workaround: Move the "Fix in release" to the 33.0 release (the one which
> matters at the end)
> * Workaround: Only put the note for the release itself

Until we can get the new logic into production, I think that yes, we'll need to implement a workaround in the data. I would actually suggest a combination of the workarounds you listed above: use the "make release specific" button in the admin on the affected note, and then change the "fixed in release" to match that release.

Comment 3

[Sylvestre Ledru [:Sylvestre]]

FYI, I implemented the workaround here:
https://www-dev.allizom.org/en-US/firefox/33.0/releasenotes/
It is now OK for the release but not for beta (less important)
https://www-dev.allizom.org/en-US/firefox/33.0beta/releasenotes/

Comment 4

[Sylvestre Ledru [:Sylvestre]]

We don't need it after all.