[wp-meta] [Making WordPress.org] #5679: Fuzzies need to be rejected in the development and the stable versions

[Making WordPress.org]

#5679: Fuzzies need to be rejected in the development and the stable versions
-------------------------------------------+--------------------
 Reporter:  carike                         |      Owner:  (none)
     Type:  defect                         |     Status:  new
 Priority:  normal                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:
-------------------------------------------+--------------------
 Example:
 https://translate.wordpress.org/projects/wp-plugins/wp-
 optimize/dev/af/default/?filters%5Bstatus%5D=either&filters%5Boriginal_id%5D=642104&filters%5Btranslation_id%5D=29842680

 Even though I already rejected this exact string for the stable version, I
 now need to go back and reject it for the development version.
 This is something that leads to a tremendous amount of extra work for GTEs
 and the work has no benefit to the GTEs, or to the community at large, but
 we have to do it, otherwise the waiting / fuzzy filter is littered with
 old translations that makes it impossible to find new contributors. I.e.
 it leads to fatigue and burn-out.

 And it makes me a **very** grumpy lion :)

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/5679>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org