Bug 9090 - Unclear that FIXED means "Fixed internally" and not "released for public"
: Unclear that FIXED means "Fixed internally" and not "released for public"
Status: NEW
Product: maemo.org Website
Bugzilla
: 5.0
: All Maemo
: Unspecified normal with 5 votes (vote)
: ---
Assigned To: unassigned
: Ferenc Szekely
:
:
:
:
  Show dependency tree
 
Reported: 2010-02-17 01:32 UTC by Andre Klapper
Modified: 2014-03-08 11:18 UTC (History)
2 users (show)

See Also:


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description Andre Klapper (reporter) maemo.org 2010-02-17 01:32:23 UTC
The current situation of setting bugs to RESOLVED FIXED when they have been
fixed internally, but not released for public creates a lot of confusion and
people reopening fixed issues because of not having read
https://bugs.maemo.org/page.cgi?id=fields.html#resolution .

PROPOSAL:
Enhance RESOLVED status by splitting resolution to something like "FIXED
INTERNALLY" and "FIXED RELEASED" or something similar.

For example Redhat Bugzilla uses "ON_QA" status for the former.
Comment 1 Lucas Maneos 2010-02-17 11:06:39 UTC
(In reply to comment #0)
> The current situation of setting bugs to RESOLVED FIXED when they have been
> fixed internally

Or even externally, for projects that are developed openly.  This is simply the
age-old "fixed in CVS" problem.

> PROPOSAL:
> Enhance RESOLVED status by splitting resolution to something like "FIXED
> INTERNALLY" and "FIXED RELEASED" or something similar.

Should be clear enough :-)

> For example Redhat Bugzilla uses "ON_QA" status for the former.

And/or RELEASE_PENDING (not sure which one maps better to Nokia's processes)