As you can see for example in http://drupal.org/node/225562#comment-1198802, our development workflow (at least for core) generally involve a last step of "update documentation". As we don't have a dedicated status for this, Dries generally ends up as putting the issue back to "Patch (code needs work)".

I suggest we add a "Fixed (needs documentation)" status and never ship a release when there are tickets in that status.

Comments

catch’s picture

catch
he/him
Primary language English
commented

Sounds good to me. Needs to be a status rather than a tag so we can track things properly - and fixed (needs documentation) will never get auto-closed.

stella’s picture

stella commented

+1 for this feature

add1sun’s picture

add1sun commented

Please. +1

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

There is a new report that treats the issue report statuses in a more general way.

Maybe it would be better to follow the topic there.

johnnoc’s picture

johnnoc
Primary language Norwegian Bokmål
Location Oslo
commented
Status: Active » Closed (duplicate)

As of time of writing, this is being addressed as "committed (needs documentation)" at #171350: Reorganise project issue statuses. IMHO, this discussion is better continued there so I am marking this issue as "duplicate".